Restyled by prettier-markdown

BatteryReporting.md

@@ -39,7 +39,7 @@ cards:
         conditions:
           - condition: state
             entity: binary_sensor.<device>_is_charging
-            state: 'on'
+            state: "on"
         chip:
           type: entity
           icon_color: yellow
@@ -55,7 +55,7 @@ cards:
         conditions:
           - condition: state
             entity: binary_sensor.<device>_is_charging
-            state: 'off'
+            state: "off"
         chip:
           type: entity
           entity: sensor.<device>_battery_level
@@ -68,7 +68,7 @@ cards:
               }
   - type: gauge
     entity: sensor.<device>_battery_level
-    unit: '%'
+    unit: "%"
     name: Watch
     needle: false
     severity:

Troubleshooting.md

@@ -10,8 +10,8 @@ You can purchase cloud-based access to your Home Assistant from [Nabu Casa](http
 
 ![Nabu Casa Setup](images/nabu_casa_setup.png)
 
-* Your API URL would be of the format `https://<id>.ui.nabu.casa/api`
-* Your Garmin Watch Menu would be of the format Menu: `https://<id>.ui.nabu.casa/local/garmin/menu.json`
+- Your API URL would be of the format `https://<id>.ui.nabu.casa/api`
+- Your Garmin Watch Menu would be of the format Menu: `https://<id>.ui.nabu.casa/local/garmin/menu.json`
 
 Where `<id>` is your personal Nabu Casa account ID.
 
@@ -23,11 +23,11 @@ Before Nabu Casa, or if you wanted to manage your own infrastructure, you might
 
 Now you have to manage:
 
-* Dynamic DNS
-* Public access via router port forwarding
-* Security via HTTPS and URL forwarding
-* Certificates for HTTPS via say [Let's Encrypt](https://letsencrypt.org/) (Nginx web server helps here)
-* Proxy allow list in `configuration.yaml` as follows:
+- Dynamic DNS
+- Public access via router port forwarding
+- Security via HTTPS and URL forwarding
+- Certificates for HTTPS via say [Let's Encrypt](https://letsencrypt.org/) (Nginx web server helps here)
+- Proxy allow list in `configuration.yaml` as follows:
 
 ```yaml
 http: