Update manage-network-function-operator.md

corrections

Author: msftadam

articles/operator-service-manager/manage-network-function-operator.md

@@ -104,16 +104,6 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
 
 #### Cluster Registry
 
-> [!NOTE]
-> * When managing a NAKS cluster with AOSM, the default parameter values enable HA as the recommended configuration.
-> * When managing a AKS cluster with AOSM, HA must be disabled using the following configuration options:
->
->```
->    --config global.networkfunctionextension.clusterRegistry.highAvailability.enabled=false
->    --config global.networkfunctionextension.webhook.highAvailability.enabled=false
->    --config global.networkfunctionextension.clusterRegistry.storageClassName=managed-csi
->```
-
 `--config global.networkfunctionextension.enableClusterRegistry=`
 * This configuration provisions a registry in the cluster to locally cache artifacts.
 * Default values enable lazy loading mode unless global.networkfunctionextension.enableEarlyLoading=true.
@@ -158,6 +148,16 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
   * Azure Stack Edge (ASE): managed-premium
 * Default value: nexus-shared.
 
+> [!NOTE]
+> * When managing a NAKS cluster with AOSM, the default parameter values enable HA as the recommended configuration.
+> * When managing a AKS cluster with AOSM, HA must be disabled using the following configuration options:
+>
+>```
+>    --config global.networkfunctionextension.clusterRegistry.highAvailability.enabled=false
+>    --config global.networkfunctionextension.webhook.highAvailability.enabled=false
+>    --config global.networkfunctionextension.clusterRegistry.storageClassName=managed-csi
+>```
+
 `--config global.networkfunctionextension.clusterRegistry.storageSize=`
 * This configuration must be provided when global.networkfunctionextension.enableClusterRegistry=true.
 * This configuration configures the size we reserve for cluster registry.
@@ -180,14 +180,14 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
 * Default value: medium.
 *  Following are the registry resource specifications for all 3 scales:
 ```
+    - requests:
+      - small: cpu: 100m, memory: 250Mi
+      - medium: cpu: 250m, memory: 500Mi
+      - large: cpu: 500m, memory: 1Gi
     - limits:
       - small: cpu: 100m, memory: 2Gi
       - medium: cpu: 500m, memory: 2Gi
       - large: cpu: 1, memory: 4Gi
-    - requests:
-      - small: cpu: 100m, memory: 250Mi
-      - mediumL cpu: 250m, memory: 500Mi
-      - large: cpu: 500m, memory: 1Gi
 ```     
 
 ## Update network function extension