Proofreading fixes

Author: joemarshallmsft

articles/operator-nexus/concepts-nexus-ipprefix.md

@@ -21,8 +21,8 @@ IP prefix resources allow operators to create a list of network prefixes with se
 
 ## Functionality
 
-The primary purpose of IP Prefix Resources is to define match criteria and action for route policies based on the network prefixes of routes. Route policies are rules that determine how routes are imported and exported between different networks, such as the infrastructure network, the workload network, and the external network. By using IP Prefix Resources, operators can control which routes are allowed or denied.
+The primary purpose of IP prefix resources is to define match criteria and actions for route policies based on the network prefixes of routes. Route policies are rules that determine how routes are imported and exported between different networks, such as the infrastructure network, the workload network, and the external network. By using IP prefix resources, operators can control which routes are allowed or denied.
 
-The conditions of a Route Policy are specified using the IP Prefix resource. This resource, modeled as an ARM resource under Microsoft.managednetworkfabric, defines the match conditions and actions for the route policy based on the IP prefix of the routes.
+The conditions of a Route Policy are specified using the IP prefix resource. This resource, modeled as an ARM resource under Microsoft.managednetworkfabric, defines the match conditions and actions for the route policy based on the IP prefix of the routes.
 
-The operator can create different combinations of IP Prefix rules to achieve different routing behaviors. For example, the operator can use the EqualTo condition to match exact prefixes, or use the NotEqualTo condition to match prefixes that aren't equal to the specified prefix. The operator can also use the `Permit` action to allow the matching prefixes, or use the `Deny` action to block the matching prefixes. The sequence number determines the order of evaluation of the rules, from lowest to highest. The operator can use the sequence number to create more specific rules before more general rules, or to create exceptions to the default rules.
+The operator can create different combinations of IP prefix rules to achieve different routing behaviors. For example, the operator can use the `EqualTo` condition to match exact prefixes, or use the `NotEqualTo` condition to match prefixes that aren't equal to the specified prefix. The operator can also use the `Permit` action to allow the matching prefixes, or use the `Deny` action to block the matching prefixes. The sequence number determines the order of evaluation of the rules, from lowest to highest. The operator can use the sequence number to create more specific rules before more general rules, or to create exceptions to the default rules.

articles/operator-nexus/how-to-ip-prefixes.md

@@ -9,47 +9,20 @@ ms.date: 02/28/2024
 ms.custom: template-how-to
 ---
 
-# Overview
+# How to Create and Manage IP Prefixes
 
 This article explains the main management operations for IP prefixes and IP prefix rules in Azure Operator Nexus.
 
-## Properties 
-
-The IpPrefix resource has the following properties: 
-
-1.  **location**: The Azure region where the resource is located. 
-
-2.  **properties**: The properties of the IpPrefix resource, which include: 
-
-    -   **configurationState**: The configuration state of the resource. 
-
-    -   **provisioningState**: The provisioning state of the resource. 
-
-    -   **administrativeState**: The administrative state of the resource. 
-
-    -   **ipPrefixRules**: A list of IP Prefix Rules. Each rule has the following properties: 
-
-        -   **action**: The action to be taken on the configuration (`Permit` or `Deny`). 
-
-        -   **sequenceNumber**: The sequence to insert to/delete from the existing route. The sequence number must be between 1 and 4294967295. 
-
-        -   **networkPrefix**: The network prefix specifying IPv4/IPv6 packets to be permitted or denied.
-
-        -   **condition**: Specifies the prefix-list bounds. Possible values are `EqualTo`, `GreaterThanOrEqualTo`, `LesserThanOrEqualTo`, and `Range`.
-
-        -   **subnetMaskLength**: Gives the minimum NetworkPrefix length to be matched. Possible values for IPv4 are 1-32. Possible values for IPv6 are 1-128. 
-
-
 ## IP prefix operations
 
 
 ### Create an IP prefix
 
 
-To create an IP Prefix resource, follow these steps: 
+To create an IP prefix resource, follow these steps: 
 
 
-1.  Specify the properties and rules of the IP Prefix resource. You can use the following azcli command as a reference: 
+1.  Specify the properties and rules of the IP prefix resource. You can use the following azcli command as a reference: 
 
     ```azurecli
     az networkfabric ipprefix create--resource-group myResourceGroup \
@@ -59,18 +32,18 @@ To create an IP Prefix resource, follow these steps: 
       --ip-prefix-rules action=Permit condition=EqualTo networkPrefix=20.20.20.0/24 sequenceNumber=20
     ```
 
-    The properties and rules of the IP Prefix resource are: 
+    The properties and rules of the IP prefix resource are: 
 
-    - `resource-group`: The name of the resource group where you want to create the IP Prefix resource. 
+    - `resource-group`: The name of the resource group where you want to create the IP prefix resource. 
 
-    -  `name`: The name of the IP Prefix resource. 
+    -  `name`: The name of the IP prefix resource. 
 
-    -  `location`: The Azure region where you want to create the IP Prefix resource. 
+    -  `location`: The Azure region where you want to create the IP prefix resource. 
 
-    -  `ip-prefix-rules`: The list of rules that define the match criteria and action for the IP Prefix resource. Each rule has the following properties: 
+    -  `ip-prefix-rules`: The list of rules that define the match criteria and action for the IP prefix resource. Each rule has the following properties: 
 
 
-        -  `action`: The action to take when the condition is met. It can be either Permit or Deny. Permit means to allow the route, and Deny means to reject the route. 
+        -  `action`: The action to take when the condition is met. It can be either `Permit` or `Deny`. `Permit` means to allow the route, and `Deny` means to reject the route. 
 
         -  `condition`: The condition to compare the network prefix of the route with the network prefix of the rule. It can be one of the following values: 
 
@@ -80,37 +53,37 @@ To create an IP Prefix resource, follow these steps: 
 
             -  `GreaterThanOrEqualTo`: The condition is true when the network prefix of the route is greater than or equal to the network prefix of the rule.
 
-        -  `networkPrefix`: The network segment to match. It's an IP address and a prefix length, such as 10.10.10.0/28 or 2001:db8::/64. 
+        -  `networkPrefix`: The network segment to match. It's an IP address and a prefix length, such as 10.10.10.0/28 or 2001:db8::/64. For IPv4, the prefix length must be 1-32. For IPv6, the prefix length must be 1-128.
 
         -  `sequenceNumber`: The order of evaluation of the rule, from lowest to highest. The rule with the lowest sequence number is evaluated first, and the rule with the highest sequence number is evaluated last. If a rule matches the route, the evaluation stops and the action of the rule is executed. If no rule matches the route, the default action is Deny. 
 
 
-2.  Create the IP Prefix resource using the azcli command. You can use the same command as in the previous step, or modify it as per your requirements.
+2.  Create the IP prefix resource using the azcli command. You can use the same command as in the previous step, or modify it as per your requirements.
 
-3.  Verify that the IP Prefix resource is created successfully. You can use the `az networkfabric ipprefix show` command to show the details of the IP Prefix resource. You can use the following example as a reference: 
+3.  Verify that the IP prefix resource is created successfully. You can use the `az networkfabric ipprefix show` command to show the details of the IP prefix resource. You can use the following example as a reference: 
 
     ```azurecli
-    networkfabric ipprefix show \
+    az networkfabric ipprefix show \
       --resource-group myResourceGroup \
       --name myIpPrefix 
     ```
 
-In this example, `myResourceGroup` is the name of the resource group where you created the IP Prefix resource, and `myIpPrefix` is the name of the IP Prefix resource. 
+In this example, `myResourceGroup` is the name of the resource group where you created the IP prefix resource, and `myIpPrefix` is the name of the IP prefix resource. 
 
-The response should contain the properties and rules of the IP Prefix resource, such as the ID, type, ipPrefixRules, location, name, provisioningState, resourceGroup, and tags. 
+The response should contain the properties and rules of the IP prefix resource, such as the ID, type, ipPrefixRules, location, name, provisioningState, resourceGroup, and tags. 
 
-### Show an IP Prefix resource
+### Show an IP prefix resource
 
-To get the details of an existing IP Prefix resource by its ID or name, use the following command: 
+To get the details of an existing IP prefix resource by its ID or name, use the following command: 
 
 ```azurecli
-# Get the details of an IP Prefix resource by its name
+# Get the details of an IP prefix resource by its name
 az networkfabric ipprefix show \
   --resource-group myResourceGroup \
   --name myIpPrefix
 ```
 
-The REST API response body for getting the details of an IP Prefix resource by its ID is as follows: 
+The REST API response body is as follows: 
 
 ```json
 {
@@ -136,13 +109,13 @@ The REST API response body for getting the details of an IP Prefix resource by i
 }
 ```
 
-### Updating an IP Prefix Resource 
+### Updating an IP prefix resource 
 
-To update an IP Prefix resource, follow these steps: 
+To update an IP prefix resource, follow these steps: 
 
-1.  Specify the properties and rules of the IP Prefix resource that you want to update. You can use the same JSON template as in the previous section, or modify it as per your requirements. 
+1.  Specify the properties and rules of the IP prefix resource that you want to update. You can use the same JSON template as in the previous section, or modify it as per your requirements. 
 
-2.  Update the IP Prefix resource using the Azure CLI command or the REST API method. You can use the following examples as a reference: 
+2.  Update the IP prefix resource using the Azure CLI command or the REST API method. You can use the following examples as a reference: 
 
     ```azurecli
     az networkfabric ipprefix update  \
@@ -151,20 +124,20 @@ To update an IP Prefix resource, follow these steps: 
       --ip-prefix-rules "[{action:Permit,sequenceNumber:4155123341,networkPrefix:'10.10.10.10/30',condition:GreaterThanOrEqualTo,subnetMaskLength:10}]"
     ```
 
-In this example, `resourceGroupName` is the name of the resource group where you created the IP Prefix resource, `ipPrefixName` is the name of the IP Prefix resource, and the `--add` option adds a new rule to the ipPrefixRules property. The new rule denies routes with network prefix 30.30.30.0/24 and has a sequence number of 30. 
+In this example, `resourceGroupName` is the name of the resource group where you created the IP prefix resource, `ipPrefixName` is the name of the IP prefix resource, and the `--add` option adds a new rule to the ipPrefixRules property. The new rule denies routes with network prefix 30.30.30.0/24 and has a sequence number of 30. 
 
-### Deleting an IP Prefix resource 
+### Deleting an IP prefix resource 
 
-To delete an existing IP Prefix resource by its ID or name, use the following command: 
+To delete an existing IP prefix resource by its ID or name, use the following command: 
 
 ```azurecli
-# Delete an IP Prefix resource by its name
+# Delete an IP prefix resource by its name
 az networkfabric ipprefix delete \
   --resource-group myResourceGroup \
   --name myIpPrefix
 ```
 
-The REST API request body for deleting an IP Prefix resource by its ID is as follows: 
+The REST API request body for deleting an IP prefix resource by its ID is as follows: 
 
 ```json
 {