updated typos

Author: sushantjrao

articles/operator-nexus/howto-append-a-custom-suffix-to-interface-descriptions.md

@@ -19,7 +19,7 @@ This guide explains how to append a user-defined suffix (`additionalDescription`
 
 ## Steps to append a custom suffix
 
-### 1. Check the current iterface description
+### 1. Check the current interface description
 
 Before making changes, verify the existing interface description using the following command:
 
@@ -59,9 +59,6 @@ az networkfabric interface update --additional-description "example-description"
 | `-g, --resource-group`   | Defines the name of the resource group where the device is located. | No specific constraints. |
 | `--resource-name`        | Indicates the name of the network interface resource. | No specific constraints. |
 
-Let me know if you'd like any further refinements! 🚀
-
-
 ### 3. Commit the configuration
 
 After updating the description, apply the changes to the fabric:
@@ -76,7 +73,6 @@ Parameter Details:
 | `--resource-group`  | `-g`      | Name of the resource group. |
 | `--resource-name`   | N/A       | Name of the Network Fabric. |
 
-Let me know if you need any modifications or additional parameters! 🚀
 ### Example
 
 #### **Original interface description:**

articles/operator-nexus/howto-configure-network-fabric-controller.md

@@ -21,11 +21,11 @@ Names, such as for resources, shouldn't contain the underscore (\_) character.
 
 ### Validate ExpressRoute circuit
 
-Validate the ExpressRoute circuit(s) for correct connectivity (CircuitID)(AuthID);  NFC provisioning would fail if connectivity is incorrect.
+Validate the ExpressRoute circuits for correct connectivity (CircuitID)(AuthID); NFC provisioning would fail if connectivity is incorrect.
 
-## VM SKU update for Network Fabric Controller  
+## Virtual Machine (VM) SKU update for Network Fabric Controller  
 
-With the latest update, all new NFC Cluster deployments will use the `Standard_D8s_v3` virtual machine SKU instead of `Standard_Ds4_v2`. 
+With the latest update, all new NFC Cluster deployments uses `Standard_D8s_v3` virtual machine SKU instead of `Standard_Ds4_v2`. 
 This change is required due to the limited availability of `Standard_Ds4_v2` in several Azure regions.
 
 > [!Note]
@@ -58,7 +58,7 @@ To check if your subscription has sufficient vCPU quota for the new SKU 'DSv3',
 
 Look for the **vCPUs** quota and ensure it meets the minimum requirement.  
 
-### Requesting additional vCPU Quota  
+### Requesting more vCPU quota  
 
 If your quota is insufficient, request an increase by:  
 
@@ -88,7 +88,7 @@ az group create -n NFCResourceGroupName -l "<Location>"
 |---------|------------------------------|----------------------------|----------------------------|------------|------|
 | Resource-Group | A resource group is a container that holds related resources for an Azure solution. | NFCResourceGroupName | XYZNFCResourceGroupName | True | String |
 | Location | The Azure Region is mandatory to provision your deployment. | eastus, westus3, southcentralus, eastus2euap | eastus | True         | String |
-| Resource-Name | The Resource-name will be the name of the Network Fabric Controller | nfcname | XYZnfcname | True         | String |
+| Resource-Name | The Resource-name is the name of the Network Fabric Controller. | nfcname | XYZnfcname | True         | String |
 | ipv4-address-space | IPv4 Network Fabric Controller Address Space, the default subnet block is 10.0.0.0/19, and it also shouldn't overlap with any of the ExpressRoute IPs | 10.0.0.0/19 | 10.0.0.0/19 | Not Required | String |
 | ipv6-address-space | IPv6 Network Fabric Controller Address Space, this parameter defaults to FC00::/59, with the permissible range being /59 | "FC00::/59" | "FC00::/59" | Not Required | String |
 | Express Route Circuits | The ExpressRoute circuit is a dedicated 10G link that connects Azure and on-premises. You need to know the ExpressRoute Circuit ID and Auth key for an NFC to successfully provision. There are two Express Route Circuits, one for the Infrastructure services and other one for Workload (Tenant) services | --infra-er-connections '[{"expressRouteCircuitId": "xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx", "expressRouteAuthorizationKey": "xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx"}]' <br /><br /> --workload-er-connections '[{"expressRouteCircuitId": "xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx", "expressRouteAuthorizationKey": "xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx"}]' | subscriptions/xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx/resourceGroups/ER-Dedicated-WUS2-AFO-Circuits/providers/Microsoft.Network/expressRouteCircuits/MSFT-ER-Dedicated-PvtPeering-WestUS2-AFO-Ckt-01", "expressRouteAuthorizationKey": "xxxxxx-xxxxxx-xxxx-xxxx-xxxxxx"}] | True         | string |
@@ -109,10 +109,11 @@ az networkfabric controller create \
 --debug --no-wait
 ```
 
-**Note:** The NFC creation takes between 30-45 mins.
-Use the `show` command to monitor NFC creation progress.
-You'll see different provisioning states such as, Accepted, updating and Succeeded/Failed.
-Delete and recreate the NFC if the creation fails (`Failed`).
+> [!Note] The NFC creation takes between 30-45 mins.
+> Use the `show` command to monitor NFC creation progress.
+> You see different provisioning states such as, Accepted, updating and Succeeded/Failed.
+> Delete and recreate the NFC if the creation fails (`Failed`).
+
 The expected output only shows running as soon as you execute via AzureCLI
 
 Expected output: