Update and rename howto-create-access-control-list-for-nni.md to howto-create-access-control-list-for-network-to-network-interconnects.md

fixed the issues as requested by the last PR review

Author: sushantjrao

articles/operator-nexus/howto-create-access-control-list-for-nni.md renamed to articles/operator-nexus/howto-create-access-control-list-for-network-to-network-interconnects.md

@@ -21,17 +21,17 @@ To create an ACL and define its properties, you can utilize the `az networkfabri
 
 1. **Set subscription (if necessary):**
 
- If you have multiple subscriptions and need to set one as the default, you can do so with:
+If you have multiple subscriptions and need to set one as the default, you can do so with:
 
- ```bash
-   az account set --subscription <subscription-id>
-   ```
+```bash
+az account set --subscription <subscription-id>
+```
 
 2. **Create ACL:**
 
-    ```bash
+```bash
     az networkfabric acl create --resource-group "<resource-group>" --location "<location>" --resource-name "<acl-name>" --annotation "<annotation>" --configuration-type "<configuration-type>" --default-action "<default-action>" --match-configurations "[{matchConfigurationName:<match-config-name>,sequenceNumber:<sequence-number>,ipAddressType:<IPv4/IPv6>,matchConditions:[{ipCondition:{type:<SourceIP/DestinationIP>,prefixType:<Prefix/Exact>,ipPrefixValues:['<ip-prefix1>', '<ip-prefix2>', ...]}}],actions:[{type:<Action>}]}]"
-    ```
+```
 
 | Parameter            | Description                                                          |
 |----------------------|----------------------------------------------------------------------|
@@ -70,12 +70,12 @@ The table below provides guidance on the usage of parameters when creating ACLs:
 | configuration-type     | Configuration type (inline or file)                        | Example: inline                 |
 
 > [!NOTE]
-> Inline ports and inline VLANs are statically defined using azcli.<br>
-> PortGroupNames and VlanGroupNames are dynamically defined.<br>
-> Combining inline ports with portGroupNames is not allowed, similarly for inline VLANs and VLANGroupNames.<br>
-> IPGroupNames and IpPrefixValues cannot be combined.<br>
-> Egress ACLs do not support certain options like IP options, IP length, fragment, ether-type, DSCP marking, and TTL values.<br>
-> Ingress ACLs do not support the following options: etherType.<br>
+> - Inline ports and inline VLANs are statically defined using azcli.<br>
+> - PortGroupNames and VlanGroupNames are dynamically defined.<br>
+> - Combining inline ports with portGroupNames is not allowed, similarly for inline VLANs and VLANGroupNames.<br>
+> - IPGroupNames and IpPrefixValues cannot be combined.<br>
+> - Egress ACLs do not support certain options like IP options, IP length, fragment, ether-type, DSCP marking, and TTL values.<br>
+> - Ingress ACLs do not support the following options: etherType.<br>
 
 ### Example payload for ACL creation