Skip to content

Commit c4ea5d5

Browse files
authored
Improve formatting in final rendering of document
Added empty lines between the numbered lists and the tip and hint boxes, as the numbered steps is getting rendered inside the preceding tip boxes on the final docs website, even though it is not the case with the markdown preview.
1 parent 1cbfae1 commit c4ea5d5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/api-management/api-management-howto-provision-self-hosted-gateway.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,13 +36,15 @@ Complete the following quickstart: [Create an Azure API Management instance](get
3636
3. Enter the **Name** and **Region** of the gateway.
3737
> [!TIP]
3838
> **Region** specifies intended location of the gateway nodes that will be associated with this gateway resource. It's semantically equivalent to a similar property associated with any Azure resource, but can be assigned an arbitrary string value.
39+
3940
4. Optionally, enter a **Description** of the gateway resource.
4041
5. Optionally, select **+** under **APIs** to associate one or more APIs with this gateway resource.
4142
> [!TIP]
4243
> You can associate and remove an API from a gateway on the API's **Settings** tab.
4344
4445
> [!IMPORTANT]
4546
> By default, none of the existing APIs will be associated with the new gateway resource. Therefore, attempts to invoke them via the new gateway will result in `404 Resource Not Found` responses.
47+
4648
6. Click **Add**.
4749

4850
Now the gateway resource has been provisioned in your API Management instance. You can proceed to deploy the gateway.

0 commit comments

Comments
 (0)