small grammar changes

Author: HollyCl

articles/operator-nexus/concepts-network-fabric-resource-update-commit.md

@@ -10,9 +10,9 @@ ms.date: 04/03/2024
 #CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
 ---
 
-# Network Fabric resource update and commit scenarios
+# Network Fabric resource update and commit operations
 
-Currently, Nexus Network Fabric resources don't support dynamic updates and the operator needs to disable a parent resource (for example, L3Isolation domain) and reput the parent or child resource with updated values and execute the administrative post action to enable and configure the devices. Network Fabric's new resource update flow allows you to  batch and update a set of Network Fabric resources via a `commitConfiguration` POST action when resources are enabled. There's no change if the user chooses the current workflow of disabling L3 Isolation domain, making changes and the enabling L3 Isolation domain. 
+Currently, Nexus Network Fabric resources require that you disable a parent resource (such as an L3Isolation domain) and reput the parent or child resource with updated values and execute the administrative post action to enable and configure the devices. Network Fabric's new resource update flow allows you to  batch and update a set of Network Fabric resources via a `commitConfiguration` POST action when resources are enabled. There's no change if the user chooses the current workflow of disabling L3 Isolation domain, making changes and the enabling L3 Isolation domain. 
 
 ## Network Fabric resource update overview
 
@@ -71,27 +71,27 @@ To successfully execute update resources, fabric must be in provisioned state. T
 | **External Network**         | Child (of L3 ISD) |   Update to properties  <br>-   Addition/Update of IPv4/IPv6 RoutePolicy <br>-   Option A properties MTU, Addition/Update of Ingress and Egress ACLs, <br>-   Option A properties – BFD Configuration <br>-   Option B properties – Route Targets <br>   Addition/Update of tags  | -   *Re-PUT* of resource. <br>-   Creating a new external network <br>-   Deleting an External network when parent Layer 3 Isolation domain is enabled. | To delete the resource, the parent resource must be disabled.<br><br> NOTE: Only one external network is supported per ISD.      |
 | **Route Policy**             | Parent            | -   Update entire statement including seq number, condition, action. <br>-   Addition/update tags   | -   *Re-PUT* of resource. <br>-   Update to Route Policy linked to a Network-to-Network Interconnect resource.   | To delete the resource, the `connectedResource` (`IsolationDomain` or N-to-N Interconnect) shouldn't hold any reference. |
 | **IPCommunity**              | Parent            |  Update entire ipCommunity rule including seq number, action, community members, well known communities.  |   *Re-PUT* of resource   | To delete the resource, the connected `RoutePolicy` Resource shouldn't hold any reference. |
-| **IPPrefixes**               | Parent            | -   Update the entire IPPrefix rule including seq number, networkPrefix, condition, subnetMask Length. <br>-   Addition/update tags  |    *Re-PUT* of resource  | To delete the resource, the connected `RoutePolicy` Resource should not hold any reference. |
-| **IPExtendedCommunity**      | Parent            | -   Update entire IPExtended community rule including seq number, action, route targets. <br>-   Addition/update tags    |  *Re-PUT* of resource      | To delete the resource, the connected `RoutePolicy` Resource should not hold any reference.|
+| **IPPrefixes**               | Parent            | -   Update the entire IPPrefix rule including seq number, networkPrefix, condition, subnetMask Length. <br>-   Addition/update tags  |    *Re-PUT* of resource  | To delete the resource, the connected `RoutePolicy` Resource shouldn't hold any reference. |
+| **IPExtendedCommunity**      | Parent            | -   Update entire IPExtended community rule including seq number, action, route targets. <br>-   Addition/update tags    |  *Re-PUT* of resource      | To delete the resource, the connected `RoutePolicy` Resource shouldn't hold any reference.|
 | **ACLs**   | Parent            | - Addition/Update to match configurations and dynamic match configurations. <br>-   Update to configuration type <br>-   Addition/updating ACLs URL <br>-   Addition/update tags   | -   *Re-PUT* of resource. <br>-   Update to ACLs linked to a Network-to-Network Interconnect resource.  | To delete the resource, the `connectedResource` (like `IsolationDomain` or N-to-N Interconnect) shouldn't hold any reference.  |
 
 ## Behavior notes and constraints
 
 - The Nexus Network Fabric update flow is disabled by default and requires you raise  a support ticket to enable the feature. 
 
-- If a parent resource is in a **disabled** administrative state and there are changes made to either to the parent or the child resources, the `commitConfiguration` action isn't applicable. Enabling the resource would push the configuration. The commit path for such resources is triggered only when the parent resource is in the **enabled** administrative state. 
+- If a parent resource is in a **Disabled** administrative state and there are changes made to either to the parent or the child resources, the `commitConfiguration` action isn't applicable. Enabling the resource would push the configuration. The commit path for such resources is triggered only when the parent resource is in the **Enabled** administrative state. 
 
-- If `commitConfiguration` fails, then the fabric remains in the **accepted** in configuration state  until the user addresses the issues and performs a successful `commitConfiguration`. Currently, only roll-forward mechanisms are provided when failure occurs.
+- If `commitConfiguration` fails, then the fabric remains in the **Accepted** in configuration state  until the user addresses the issues and performs a successful `commitConfiguration`. Currently, only roll-forward mechanisms are provided when failure occurs.
 
-- If the Fabric configuration is in an **accepted** state and has updates to Azure Resource Manager resources yet to be committed, then no administrative action is allowed on the resources. 
+- If the Fabric configuration is in an **Accepted** state and has updates to Azure Resource Manager resources yet to be committed, then no administrative action is allowed on the resources. 
 
-- If the Fabric configuration is in an **accepted** state and has updates to Azure Resource Manager resources yet to be committed, then delete operation on supported resources can't be triggered. 
+- If the Fabric configuration is in an **Accepted** state and has updates to Azure Resource Manager resources yet to be committed, then delete operation on supported resources can't be triggered. 
 
 - Creation of parent resources is independent of `commitConfiguration` and the update flow. *Re-PUT* of resources isn't supported on any resource. 
 
 - Network Fabric resource update is supported for both Greenfield deployments and Brownfield deployments but with some constraints. 
 
-    - In Greenfield scenario, the Fabric configuration state is **accepted**  once there are any updates done Network Fabric resources. Once the `commitConfiguration` action is triggered, it moves to either **Provisioned** or **Accepted** state depending on success or failure of the action.  
+    - In Greenfield scenario, the Fabric configuration state is **Accepted**  once there are any updates done Network Fabric resources. Once the `commitConfiguration` action is triggered, it moves to either **Provisioned** or **Accepted** state depending on success or failure of the action.  
 
     - In Brownfield scenario, commitConfiguration action is supported but the supported Network Fabric resources (such as Isolation domains, Internal Networks, RoutePolicy & ACLs) must be created using GA version of the API (2023-06-15). This temporary restriction is relaxed following the migration of all resources to the latest GA version. 
 
@@ -103,7 +103,7 @@ To successfully execute update resources, fabric must be in provisioned state. T
 
 - Update of new Route policies and ACLs might cause traffic disruption depending on the rules applied.  
 
-- Use a list command on the specific resource type (list all resources of an internal network type) to verify the resources that are updated and are not committed to device. The resources that have an **accepted** or **rejected** configuration state can be filtered and identified as resources that are yet to be committed or where the commit to device fails. 
+- Use a list command on the specific resource type (list all resources of an internal network type) to verify the resources that are updated and aren't committed to device. The resources that have an **Accepted** or **Rejected** configuration state can be filtered and identified as resources that are yet to be committed or where the commit to device fails. 
 
 For example: