Fix partial formatting

Author: maxvp

src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx

@@ -6,39 +6,43 @@ import { Tabs, TabItem, Render } from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
+
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications**.
 2. Select **Add an application**.
 3. Select **Infrastructure**.
 4. Enter any name for the application.
 5. In **Target criteria**, select the target hostname(s) that will represent the application. The application definition will apply to all targets that share the selected hostname, including any targets added in the future.
 6. Enter the **Protocol** and **Port** that will be used to connect to the server.
 7. (Optional) If a protocol runs on more than one port, select **Add new target criteria** and reconfigure the same target hostname and protocol with a different port number.
-	:::note
-	Access for Infrastructure only supports assigning one protocol per port. You can reuse a port/protocol pairing across infrastructure applications, but the port cannot be reassigned to another protocol.
-	:::
+   :::note
+   Access for Infrastructure only supports assigning one protocol per port. You can reuse a port/protocol pairing across infrastructure applications, but the port cannot be reassigned to another protocol.
+   :::
 8. Select **Next**.
 9. To secure your targets, configure a policy that defines who can connect and how they can connect:
-	1. Enter any name for your policy.
-	2. Create a rule that matches the users who are allowed to reach the targets. For more information, refer to [Access policies](/cloudflare-one/policies/access/) and review the list of [infrastructure policy selectors](/cloudflare-one/applications/non-http/infrastructure-apps/#infrastructure-policy-selectors).
-	3. In **Connection context**, configure the following settings:
-		- **SSH user**: Enter the UNIX usernames that users can log in as (for example, `root` or `ec2-user`).
-		- **Allow users to log in as their email alias**: (Optional) When selected, users who match your policy definition will be able to access the target using their email address prefix. For example, `[email protected]` could log in as `jdoe`.
 
-    	:::note
-    	Cloudflare will not create new users on the target. UNIX users must already be present on the server.
-    	:::
+   1. Enter any name for your policy.
+   2. Create a rule that matches the users who are allowed to reach the targets. For more information, refer to [Access policies](/cloudflare-one/policies/access/) and review the list of [infrastructure policy selectors](/cloudflare-one/applications/non-http/infrastructure-apps/#infrastructure-policy-selectors).
+   3. In **Connection context**, configure the following settings:
+
+      - **SSH user**: Enter the UNIX usernames that users can log in as (for example, `root` or `ec2-user`).
+      - **Allow users to log in as their email alias**: (Optional) When selected, users who match your policy definition will be able to access the target using their email address prefix. For example, `[email protected]` could log in as `jdoe`.
 
-4. Select **Add application**.
+      :::note
+      Cloudflare will not create new users on the target. UNIX users must already be present on the server.
+      :::
 
-   </TabItem>
+10. Select **Add application**.
+
+</TabItem>
 <TabItem label="API">
 
 1. [Create an API token](/fundamentals/api/get-started/create-token/) with the following permissions:
-   | Type | Item | Permission |
-   | ------- | ---------------- | ---------- |
-   | Account | Access: Apps & Policies | Edit |
 
-1. Make a `POST` request to the [Access applications](/api/resources/zero_trust/subresources/access/subresources/applications/methods/create/) endpoint:
+   | Type    | Item                    | Permission |
+   | ------- | ----------------------- | ---------- |
+   | Account | Access: Apps & Policies | Edit       |
+
+2. Make a `POST` request to the [Access applications](/api/resources/zero_trust/subresources/access/subresources/applications/methods/create/) endpoint:
 
    ```sh
    curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/apps \
@@ -110,27 +114,27 @@ import { Tabs, TabItem, Render } from "~/components";
 
 3.  Use the [`cloudflare_zero_trust_access_policy`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.45.0/docs/resources/zero_trust_access_policy) resource to add an infrastructure policy to the application:
 
-        ```tf
-        resource "cloudflare_zero_trust_access_policy" "infra-app-policy" {
-        	application_id = cloudflare_zero_trust_access_application.infra-app.id
-        	account_id = var.cloudflare_account_id
-        	name       = "Allow a specific email"
-        	decision   = "allow"
-        	precedence = 1
-
-        	include {
-        		email = ["[email protected]"]
-        	}
-
-        	connection_rules {
-        		ssh {
-        			usernames = ["root", "ec2-user"]
-        		}
-        	}
-        }
-        ```
-
-    </TabItem>
+            ```tf
+            resource "cloudflare_zero_trust_access_policy" "infra-app-policy" {
+            	application_id = cloudflare_zero_trust_access_application.infra-app.id
+            	account_id = var.cloudflare_account_id
+            	name       = "Allow a specific email"
+            	decision   = "allow"
+            	precedence = 1
+
+            	include {
+            		email = ["[email protected]"]
+            	}
+
+            	connection_rules {
+            		ssh {
+            			usernames = ["root", "ec2-user"]
+            		}
+            	}
+            }
+            ```
+
+</TabItem>
 </Tabs>
 
 The targets in this application are now secured by your infrastructure policies.