anchor.diff:  Complete the steps to modify the relevant configuration only if the default behavior of the Operator is not compatible with your use case.
   ====
   
  -The SR-IOV Network Operator adds the `SriovOperatorConfig.sriovnetwork.openshift.io` Custom Resource Definition (CRD) to {product-title}.
  -You can configure the SR-IOV software compoenents by modifying the default 
  -SriovOperatorConfig Custom Resource (CR). The Operator supports the following optional behavioral changes:
  -
  -- Disabling the Network Resources Injector
  -- Disabling the Operator admission web controller
  -- Configuring a custom node selector for the SR-IOV Network Config daemon. The daemon runs on all the worker nodes by default.
  +The SR-IOV Network Operator adds the `SriovOperatorConfig.sriovnetwork.openshift.io` CustomResourceDefinition resource.
  +The operator automatically creates a SriovOperatorConfig custom resource (CR) named `default` in the `openshift-sriov-network-operator` namespace.
   
   [NOTE]
   =====
  -There is one Custom Resource of SriovOperatorConfig being created when
  -the operator is up. Change the operator configuration by modifying this
  -pre-created Custom Resource. The `default` Custom Resource is created in
  -`openshift-sriov-network-operator` namespace.
  +The `default` CR contains the SR-IOV Network Operator configuration for your cluster.
  +To change the operator configuration, you must modify this CR.
   =====
   
  -`SriovOperatorConfig` provides three options for configuring operator:
  -* `enableInjector` allows project administrators to enable or disable Network
  -Resources Injector DaemonSet.
  -* `enableOperatorWebhook` allows project adminstrators to enable or disable
  -Operator Admission Controller Webhook DaemonSet.
  -* `configDaemonNodeSelector` allows project adminstrators to schedule SR-IOV
  -Network Config Daemon on selected nodes.
  +The SriovOperatorConfig CR provides several fields for configuring the operator:
   
  +* `enableInjector` allows project administrators to enable or disable the Network Resources Injector DaemonSet.
  +* `enableOperatorWebhook` allows project administrators to enable or disable the Operator Admission Controller webook DaemonSet.
  +* `configDaemonNodeSelector` allows project administrators to schedule the SR-IOV Network Config Daemon on selected nodes.
   
  -[id="disabling-network-resource-injector_{context}"]
  -== Disabling Network Resources Injector
  +[id="about-network-resource-injector_{context}"]
  +== About the Network Resources Injector
   
   The Network Resources Injector is a Kubernetes Dynamic Admission Controller 
  -application that:
  +application. It provides the following capabilities:
   
  -* Mutates resource requests and limits in pod specifiction to add SR-IOV
  -resource name according to SR-IOV network attachment definition annotation.
  -* Mutates pod specifications with downward API volume to expose pod annotations
  -and labels to the running container as files under `/etc/podnetinfo`.
  +* Mutation of resource requests and limits in Pod specification to add an SR-IOV resource name according to an SR-IOV network attachment definition annotation.
  +* Mutation of Pod specifications with downward API volume to expose pod annotations and labels to the running container as files under the `/etc/podnetinfo` path.
   
  -By default the Network Resources Injector will be enabled by SR-IOV operator
  -and runs as a Kubernetes DaemonSet on all master nodes. Below is an example
  -of Network Resources Injector pods running in a cluster with three master
  -nodes:
  +By default the Network Resources Injector is enabled by the SR-IOV operator and runs as a DaemonSet on all master nodes. The following is an example of Network Resources Injector Pods running in a cluster with three master nodes:
   
   ----
   $ oc get pods -n openshift-sriov-network-operator
  
positive.code: network-resources-injector-lktz5          1/1     Running   0          10m
  ----
  
  Follow this procedure to disable it.
  
  .Prerequisites
  
  * Install the OpenShift Command-line Interface (CLI), commonly known as `oc`.
  * Log in as a user with `cluster-admin` privileges.
  * You must have installed the SR-IOV Operator.
  
  .Procedure
  . Update the default SriovOperatorConfig Custom Resource
  +
  ----
  $ oc patch sriovoperatorconfig default --patch '{ "spec": { "enableInjector": false}}' --type=merge -n openshift-sriov-network-operator
  ----
  
  . To re-enable Network Resources Injector
  +
  ----
  $ oc patch sriovoperatorconfig default --patch '{ "spec": { "enableInjector": true}}' --type=merge -n openshift-sriov-network-operator
  ----
  
  [id="disabling-sr-iov-operator-admission-control-webhook_{context}"]
  == Disabling SR-IOV Operator admission controller webhook
  The SRIOV Operator Admission Controller Webhook is a Kubernetes Dynamic
  Admission Controller application that:
  
  * Validating the `SriovNetworkNodePolicy` Custom Resource when it being created
  or updated.
  * Mutating the `SriovNetworkNodePolicy` Custom Resource by setting the default
  value to `priority` and `deviceType` when it being created or updated.
  
  By default the SR-IOV Operator Admission Controller Webhook will be enabled by
  the operator and runs as a Kubernetes DaemonSet on all master nodes. Below is
  an example of Operator Admission Controller Webhook pods running in a cluster
  with three master nodes:
  
  ----
  $ oc get pods -n openshift-sriov-network-operator
  
negative.code: operator-webhook-rpfrl                    1/1     Running   0          16m
  ----
  
  [id="about-custom-node-selectors_{context}"]
  == About custom node selectors
  
  The SR-IOV Network Config daemon discovers and configures the SR-IOV network devices on cluster nodes.
  By default, it is deployed to all the `worker` nodes in the cluster.
  You can use node labels to specify on which nodes the SR-IOV Network Config daemon runs.
  
  [id="disable-enable-network-resource-injector_{context}"]
  == Disabling or enabling the Network Resources Injector
  
  To disable or enable the Network Resources Injector, which is enabled by default, complete the following procedure.
  
  .Prerequisites
  
  