Skip to content

Commit

Permalink
Yep conflicts resolved
Browse files Browse the repository at this point in the history
  • Loading branch information
LivingSynthesis committed Jan 17, 2025
1 parent d570b97 commit 79c1cb1
Showing 1 changed file with 10 additions and 8 deletions.
18 changes: 10 additions & 8 deletions docs/duo_upgrade_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,16 @@ parent: Duo Guide
}
</style>

<div class= warning-box style="text-align: center; margin: 20px">
<div style="text-align: center; margin: 20px">
<h1 style="color:orange;">⚠ <b style="color:red;">Warning</b> ⚠<br></h1>
<h2>Upgrading Duos <i>can</i> cause damage to them if you do not follow instructions!
Be patient, careful, and double-check instuctions before proceeding.

StoneOrbits is not responsible for damage caused this way.</h2>
</div>

{: .warning}
Upgrading Duos <i>can</i> cause damage to them if you do not follow instructions!
Be patient, careful, and double-check instuctions before proceeding.
StoneOrbits is not responsible for damage caused this way.


---

# Duo Upgrade Guide
Expand Down Expand Up @@ -68,9 +70,9 @@ With your Duo, Chromadeck, Chromalink, Computer, and USB-C cable ready, proceed
</div>

{: .warning}
Failure to remove the battery before connecting to the Chromalink will cause the battery's lifespan to shorten dramatically.
Removing the battery incorrectly can break the battery connector, rendering the chip broken and unusable.
StoneOrbits is not responsible for any damage to the Duo or battery caused this way.
- Failure to remove the battery before connecting to the Chromalink will cause the battery's lifespan to shorten dramatically.
- Removing the battery incorrectly can break the battery connector, rendering the chip broken and unusable.
- StoneOrbits is not responsible for any damage to the Duo or battery caused this way.


- In order to safely update the Duo, the battery must be carefully disconnected first.
Expand Down

0 comments on commit 79c1cb1

Please sign in to comment.