diff --git a/source/_integrations/habitica.markdown b/source/_integrations/habitica.markdown
index b5abb3922a0..7b1c1ca31f3 100644
--- a/source/_integrations/habitica.markdown
+++ b/source/_integrations/habitica.markdown
@@ -49,7 +49,7 @@ url:
   description: "URL to your Habitica instance, if you are hosting your own"
   required: false
   type: string
-  default: http://habitica.com
+  default: https://habitica.com
 sensors:
   description: List of sensors to generate for this user. If you don't specify this entry then the default (all sensors) will be generated. If you specify this entry empty then no sensors will be generated.
   required: false
@@ -84,7 +84,7 @@ So let's call the API on `habitica.api_call`.
 
 * The `name` key becomes `xxxNotAValidNickxxx`.
 * The `path` key is trickier.
-  * Remove 'https://habitica.com/api/v3/' at the beginning of the endpoint URL.
+  * Remove `https://habitica.com/api/v3/` at the beginning of the endpoint URL.
   * Split the remaining on slashes (/) and **append the lowercase method** at the end.
   * You should get `["tasks", "user", "post"]`. To get a better idea of the API you are recommended to try all of the API calls in IPython console [using this package](https://github.com/ASMfreaK/habitipy/blob/master/README.md).
 * The `args` key is more or less described in the [docs](https://habitica.com/apidoc/).
diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown
index 08aa479bfc7..21e1396fcaf 100644
--- a/source/_integrations/html5.markdown
+++ b/source/_integrations/html5.markdown
@@ -341,5 +341,5 @@ If you need to verify domain ownership with Google Webmaster Central/Search Cons
 2. Create a directory named `www` in your Home Assistant configuration directory (`/config/` share from Samba add-on).
 3. Place the downloaded `google*.html` file in the `www` directory.
 4. RESTART Home Assistant. **This is important!**
-5. Verify the file can be accessed in the browser, e.g., **https://example.com:8123/local/google123456789.html** (change filename). You should see a plain text message saying "google-site-verification: ...". If you see "404: Not Found" or something else, retry the above steps.
+5. Verify the file can be accessed in the browser, e.g., `https://example.com:8123/local/google123456789.html` (change filename). You should see a plain text message saying "google-site-verification: ...". If you see "404: Not Found" or something else, retry the above steps.
 6. Go back to Google Webmaster Central/Search Console and proceed with the verification.