chore(docs): rephrase for a more inclusive description

src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure.mdx

@@ -59,7 +59,7 @@ Take a look at the following to make sure you're ready:
 * If custom manifests have been used instead of Helm, you will need to first remove the old installation using `kubectl delete -f previous-manifest-file.yml`, and then proceed through the guided installer again. This will generate an updated set of manifests that can be deployed using `kubectl apply -f manifest-file.yml`.
 * Make sure you are using the supported Kubernetes versions and make sure to check out the preliminary notes for your managed services or platforms on our [compatibility and requirements page](/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements).
 * Make sure you have New Relic <InlinePopover type="licenseKey" />. You can set up an account that's free&mdash;no credit card required.
-* Make sure you whitelist the domains ([newrelic dockerhub](https://hub.docker.com/u/newrelic) and Google's registry `registry.k8s.io`) from where the installation will pull container images. Note, you may need to follow the [commands](https://kubernetes.io/blog/2023/03/10/image-registry-redirect/#how-can-i-check-if-i-am-impacted) to identify the additional Google registry domain to be whitelisted, because `registry.k8s.io` is typically redirected to your local registry domain (e.g., `asia-northeast1-docker.pkg.dev`) based on your region.
+* Make sure the newrelic dockerhub (`https://hub.docker.com/u/newrelic`) and Google's registry (`registry.k8s.io`) domains are added to your allow list. This is where the installation will pull container images from. Note, you may need to follow the [commands](https://kubernetes.io/blog/2023/03/10/image-registry-redirect/#how-can-i-check-if-i-am-impacted) to identify the additional Google registry domains to be added to your white list, because `registry.k8s.io` is typically redirected to your local registry domain (e.g., `asia-northeast1-docker.pkg.dev`) based on your region.
 
 ## Start the guided install [#how-to-start]
 
@@ -443,11 +443,11 @@ Before starting our [guided install](https://one.newrelic.com/nr1-core?state=51f
        oc adm policy add-scc-to-user privileged system:serviceaccount:<namespace>:<release_name>-nrk8s-controlplane
        oc adm policy add-scc-to-user privileged system:serviceaccount:<namespace>:default
        ```
-       
+
        <Callout variant="tip">
         The default `release_name` provided by the installer is `newrelic-bundle`. The default `namespace` is `newrelic`.
        </Callout>
-       
+
     2. Complete the steps in our [guided install](https://one.newrelic.com/nr1-core?state=51fbbd48-c8ca-ead9-bb90-af96e18d82a7).
     3. If you're using signed certificates, make sure they are properly configured by using the following variables in the `DaemonSet` portion of your manifest, to set the `.pem` file:
       ```yaml
@@ -457,7 +457,7 @@ Before starting our [guided install](https://one.newrelic.com/nr1-core?state=51f
         - name: NRIA_CA_BUNDLE_FILE
           value: YOUR_CA_BUNDLE_NAME
       ```
-    4. Set your YAML key path to `spec.template.spec.containers.name.env`. 
+    4. Set your YAML key path to `spec.template.spec.containers.name.env`.
     5. Save your changes.
 
   </Collapser>
@@ -470,7 +470,7 @@ Before starting our [guided install](https://one.newrelic.com/nr1-core?state=51f
     The Kubernetes integration only monitors worker nodes in the Azure Kubernetes Service as Azure abstracts the management of master nodes away from the Kubernetes platform.
 
   </Collapser>
-  
+
 </CollapserGroup>
 
 <InstallFeedback />