docs: Fix formatting of integration-docs-guide.md

templates/zerver/api/integration-docs-guide.md

@@ -70,16 +70,19 @@ Here are a few common macros used to document Zulip's integrations:
 
 * **Contents:**
   See [source][1].
+
     **Note:** `{{ integration_display_name }}` is replaced by
     [Integration.display_name][2] and `{{ recommended_stream_name }}`
     is replaced by [Integration.stream_name][3].
 
 * **Example usage:**
+
     ```
     {!create-stream.md!}
     ```
 
 * **Example rendering:**
+
 ```text
 First, create the stream you would like to use for GitLab notifications,
 and subscribe all interested parties to this stream. We recommend the
@@ -97,7 +100,9 @@ Here are a few common macros used to document Zulip's integrations:
   generated automatically for every webhook by using attributes in the
   [WebhookIntegration][4] class.
 
-* **Contents:** See [source][5]. **Note:** If special configuration is
+* **Contents:** See [source][5].
+
+    **Note:** If special configuration is
     required to set up the URL and you can't use this macro, be sure to use the
     `{{ api_url }}` template variable, so that your integration
     documentation will provide the correct URL for whatever server it is
@@ -105,13 +110,15 @@ Here are a few common macros used to document Zulip's integrations:
     variable, you should document that too.
 
 * **Example usage:**
+
     ```
     {!create-bot-construct-url.md!}
     ```
   Usually used right after `{!create-stream!}`.
 
 * **Example rendering:**
-  ```
+
+```text
 Next, on your Zulip settings page, create a bot for GitLab. Construct
 the URL for the GitLab bot using the bot API key and stream name:
 
@@ -130,11 +137,13 @@ Here are a few common macros used to document Zulip's integrations:
 * **Contents:** See [source][6].
 
 * **Example usage:** Usually used right after `{!create-bot-construct-url.md!}`.
+
     ```
     {!append-stream-name.md!}
     ```
 
 * **Example rendering:**
+
 ```
 To specify the stream, you must explicitly append
 `&stream=stream_name` to the end of the above URL, where
@@ -149,11 +158,13 @@ Here are a few common macros used to document Zulip's integrations:
 * **Contents:** See [source][7].
 
 * **Example usage:** Usually used right after `{!create-bot-construct-url.md!}`.
+
     ```
     {!append-topic.md!}
     ```
 
 * **Example rendering:**
+
 ```
 To change the topic used by the bot, simply append `&topic=name`
 to the end of the above URL, where `name` is your topic.
@@ -168,11 +179,13 @@ Here are a few common macros used to document Zulip's integrations:
 
 * **Example usage:** Usually used at the end of the documentation, right
   before the sample message screenshot.
+
     ```
     {!congrats.md!}
     ```
 
 * **Example rendering:**
+
 ```
 **Congratulations! You're done!**
 
@@ -188,11 +201,13 @@ Here are a few common macros used to document Zulip's integrations:
 
 * **Example usage:** Currently mostly used in non-webhook integrations docs
   under `templates/zerver/integrations/<integration_name>.md`.
+
     ```
     {!download-python-bindings.md!}
     ```
 
 * **Example rendering:**
+
 ``` text
 Download and install our [Python bindings and example scripts](/api)
 on the server where the IntegrationName bot will live.
@@ -207,11 +222,13 @@ Here are a few common macros used to document Zulip's integrations:
 
 * **Example usage:** Usually used in non-webhook integration docs under
   `templates/zerver/integrations/<integration_name>.md`.
+
     ```
     {!change-zulip-config-file.md!}
     ```
 
 * **Example rendering:**
+
 ```
 On your Zulip settings page, create a bot for Codebase.
 
@@ -233,6 +250,7 @@ Here are a few common macros used to document Zulip's integrations:
   [git-webhook-url-with-branches][13].
 
 * **Example usage:** Used exclusively in Git integrations.
+
     ```
     {!git-append-branches.md!}
     {!git-webhook-url-with-branches.md!}
@@ -249,6 +267,7 @@ Here are a few common macros used to document Zulip's integrations:
 
 * `{!webhook-url-with-bot-email.md!}` - Used in certain non-webhook integrations
   to generate URLs of the form (see [source][14]):
+
     ```
     https://bot_email:bot_api_key@yourZulipDomain.zulipchat.com/api/v1/external/beanstalk
     ```