diff --git a/docs/user/resources/04-10-iprange.md b/docs/user/resources/04-10-iprange.md
index 1d03a7ff..997c8f69 100644
--- a/docs/user/resources/04-10-iprange.md
+++ b/docs/user/resources/04-10-iprange.md
@@ -1,7 +1,7 @@
 # IpRange Custom Resource
 
 The `iprange.cloud-resources.kyma-project.io` custom resource (CR) specifies the VPC network
-IP range that is used for IP address allocation for cloud resources that require an IP address. 
+IP range that is used for IP address allocation for cloud resources that require an IP address.
 
 You are allowed to have one IpRange CR. If there are multiple IpRange resources in the cluster, the
 oldest one is reconciled and the other is ignored and put into the `Error` state.
diff --git a/docs/user/resources/04-30-20-aws-vpc-peering.md b/docs/user/resources/04-30-20-aws-vpc-peering.md
index 31b3f301..54767b60 100644
--- a/docs/user/resources/04-30-20-aws-vpc-peering.md
+++ b/docs/user/resources/04-30-20-aws-vpc-peering.md
@@ -19,7 +19,7 @@ Use the following table to identify Cloud Manager principal based on your Kyma l
 | https://canary.cockpit.btp.int.sap | https://dashboard.stage.kyma.cloud.sap | `arn:aws:iam::194230256199:user/cloud-manager-peering-stage` |
 | https://emea.cockpit.btp.cloud.sap | https://dashboard.kyma.cloud.sap       | `arn:aws:iam::194230256199:user/cloud-manager-peering-prod`  |
 
-1.  Create a new role named **CloudManagerPeeringRole** with a trust policy that allows Cloud Manager principal to assume the role:
+1. Create a new role named **CloudManagerPeeringRole** with a trust policy that allows Cloud Manager principal to assume the role:
 
     ```json
     {
@@ -37,7 +37,8 @@ Use the following table to identify Cloud Manager principal based on your Kyma l
 
     ```
 
-2.  Create a new managed policy **CloudManagerPeeringAccess** with the following permissions:
+2. Create a new managed policy **CloudManagerPeeringAccess** with the following permissions:
+
     ```json
     {
         "Version": "2012-10-17",
@@ -59,9 +60,9 @@ Use the following table to identify Cloud Manager principal based on your Kyma l
     }
     ```
 
-3.  Attach the **CloudManagerPeeringAccess** policy to the **CloudManagerPeeringRole**:
+3. Attach the **CloudManagerPeeringAccess** policy to the **CloudManagerPeeringRole**:
 
-### Deleting `AwsVpcPeering`
+## Deleting `AwsVpcPeering`
 
 Kyma's underlying cloud provider VPC peering connection is deleted as a part of AwsVpcPeering deletion. The remote VPC 
 peering connection is left hanging, and must be deleted manually.