updated docs based on feedback

neuvector · Jan 30, 2025 · 91c8019 · 91c8019
1 parent 78e10b0
commit 91c8019
Show file tree

Hide file tree

Showing 4 changed files with 28 additions and 28 deletions.
diff --git a/docs/02.deploying/09.airgap/09.airgap.md b/docs/02.deploying/09.airgap/09.airgap.md
@@ -5,7 +5,7 @@ taxonomy:
 slug: /deploying/airgap
 ---
 
-### Prerequistes
+### Prerequisites
 
 We need to install two tools to easily airgap everything for NeuVector...
 
@@ -22,18 +22,18 @@ curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 |
 
 ### Fetch the Images and Helm Chart
 
-In order to get the required container images and helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this... feel free to use either method...
+In order to get the required container images and Helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this using either method.
 
 #### For Supported Customers...
 
-If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch the all the artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
+If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch all artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
 
 #### Fetching with Commands
 
 ```bash
 # set the neuvector version
-export vNeuVector=5.4.1
-export vNeuVectorHelm=2.8.3
+export vNeuVector=5.4.2
+export vNeuVectorHelm=2.8.4
 
 # fetch the images
 helm repo add neuvector https://neuvector.github.io/neuvector-helm
@@ -54,8 +54,8 @@ hauler store add chart core --repo https://neuvector.github.io/neuvector-helm --
 #### Fetching with Declarative Manifests
 ```bash
 # set the neuvector version
-export vNeuVector=5.4.1
-export vNeuVectorHelm=2.8.3
+export vNeuVector=5.4.2
+export vNeuVectorHelm=2.8.4
 
 # create the declarative manifest
 cat << EOF >> hauler-neuvector-airgap.yaml
@@ -97,12 +97,12 @@ root@hauler-neuvector-airgap hauler % hauler store info
 +--------------------------------------------+-------+-------------+----------+----------+
 | REFERENCE                                  | TYPE  | PLATFORM    | # LAYERS | SIZE     |
 +--------------------------------------------+-------+-------------+----------+----------+
-| hauler/core:2.8.3                          | chart | -           |        1 | 33.3 kB  |
-| index.docker.io/neuvector/controller:5.4.1 | image | linux/amd64 |        7 | 255.8 MB |
+| hauler/core:2.8.4                          | chart | -           |        1 | 33.3 kB  |
+| index.docker.io/neuvector/controller:5.4.2 | image | linux/amd64 |        7 | 255.8 MB |
 |                                            | image | linux/arm64 |        7 | 244.9 MB |
-| index.docker.io/neuvector/enforcer:5.4.1   | image | linux/amd64 |        7 | 248.2 MB |
+| index.docker.io/neuvector/enforcer:5.4.2   | image | linux/amd64 |        7 | 248.2 MB |
 |                                            | image | linux/arm64 |        7 | 236.6 MB |
-| index.docker.io/neuvector/manager:5.4.1    | image | linux/amd64 |        8 | 215.7 MB |
+| index.docker.io/neuvector/manager:5.4.2    | image | linux/amd64 |        8 | 215.7 MB |
 |                                            | image | linux/arm64 |        8 | 223.3 MB |
 | index.docker.io/neuvector/scanner:latest   | image | linux/amd64 |        5 | 260.5 MB |
 |                                            | image | linux/arm64 |        5 | 256.3 MB |
@@ -141,12 +141,12 @@ root@hauler-neuvector-airgap hauler % hauler store info
 +--------------------------------------------+-------+-------------+----------+----------+
 | REFERENCE                                  | TYPE  | PLATFORM    | # LAYERS | SIZE     |
 +--------------------------------------------+-------+-------------+----------+----------+
-| hauler/core:2.8.3                          | chart | -           |        1 | 33.3 kB  |
-| index.docker.io/neuvector/controller:5.4.1 | image | linux/amd64 |        7 | 255.8 MB |
+| hauler/core:2.8.4                          | chart | -           |        1 | 33.3 kB  |
+| index.docker.io/neuvector/controller:5.4.2 | image | linux/amd64 |        7 | 255.8 MB |
 |                                            | image | linux/arm64 |        7 | 244.9 MB |
-| index.docker.io/neuvector/enforcer:5.4.1   | image | linux/amd64 |        7 | 248.2 MB |
+| index.docker.io/neuvector/enforcer:5.4.2   | image | linux/amd64 |        7 | 248.2 MB |
 |                                            | image | linux/arm64 |        7 | 236.6 MB |
-| index.docker.io/neuvector/manager:5.4.1    | image | linux/amd64 |        8 | 215.7 MB |
+| index.docker.io/neuvector/manager:5.4.2    | image | linux/amd64 |        8 | 215.7 MB |
 |                                            | image | linux/arm64 |        8 | 223.3 MB |
 | index.docker.io/neuvector/scanner:latest   | image | linux/amd64 |        5 | 260.5 MB |
 |                                            | image | linux/arm64 |        5 | 256.3 MB |
@@ -183,7 +183,7 @@ hauler store serve registry
 
 ### Deploy with Helm
 
-Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to tweak the below example for your environment...
+Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to adjust the below example for your environment.
 
 ```bash
 # set registry url

diff --git a/versioned_docs/version-5.2/02.deploying/09.airgap/09.airgap.md b/versioned_docs/version-5.2/02.deploying/09.airgap/09.airgap.md
@@ -5,7 +5,7 @@ taxonomy:
 slug: /deploying/airgap
 ---
 
-### Prerequistes
+### Prerequisites
 
 We need to install two tools to easily airgap everything for NeuVector...
 
@@ -22,11 +22,11 @@ curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 |
 
 ### Fetch the Images and Helm Chart
 
-In order to get the required container images and helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this... feel free to use either method...
+In order to get the required container images and Helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this using either method.
 
 #### For Supported Customers...
 
-If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch the all the artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
+If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch all artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
 
 #### Fetching with Commands
 
@@ -183,7 +183,7 @@ hauler store serve registry
 
 ### Deploy with Helm
 
-Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to tweak the below example for your environment...
+Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to adjust the below example for your environment.
 
 ```bash
 # set registry url

diff --git a/versioned_docs/version-5.3/02.deploying/09.airgap/09.airgap.md b/versioned_docs/version-5.3/02.deploying/09.airgap/09.airgap.md
@@ -5,7 +5,7 @@ taxonomy:
 slug: /deploying/airgap
 ---
 
-### Prerequistes
+### Prerequisites
 
 We need to install two tools to easily airgap everything for NeuVector...
 
@@ -22,11 +22,11 @@ curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 |
 
 ### Fetch the Images and Helm Chart
 
-In order to get the required container images and helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this... feel free to use either method...
+In order to get the required container images and Helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this using either method.
 
 #### For Supported Customers...
 
-If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch the all the artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
+If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch all artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
 
 #### Fetching with Commands
 
@@ -183,7 +183,7 @@ hauler store serve registry
 
 ### Deploy with Helm
 
-Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to tweak the below example for your environment...
+Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to adjust the below example for your environment.
 
 ```bash
 # set registry url

diff --git a/versioned_docs/version-5.4/02.deploying/09.airgap/09.airgap.md b/versioned_docs/version-5.4/02.deploying/09.airgap/09.airgap.md
@@ -5,7 +5,7 @@ taxonomy:
 slug: /deploying/airgap
 ---
 
-### Prerequistes
+### Prerequisites
 
 We need to install two tools to easily airgap everything for NeuVector...
 
@@ -22,11 +22,11 @@ curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 |
 
 ### Fetch the Images and Helm Chart
 
-In order to get the required container images and helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this... feel free to use either method...
+In order to get the required container images and Helm chart for NeuVector, we are able to utilize `hauler` to easily fetch, package, and distribute all the bits. We can utilize commands or declarative manifests within `hauler` to do this using either method.
 
 #### For Supported Customers...
 
-If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch the all the artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
+If you are a **Rancher Prime** or **Rancher Government Carbide** customer, please make sure to use the commands that fetch all artifacts from the respective private registry. If you're a supported customer and do not know the correct `<registry-url>` for Prime or Carbide, please contact your respective support team!
 
 #### Fetching with Commands
 
@@ -183,7 +183,7 @@ hauler store serve registry
 
 ### Deploy with Helm
 
-Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to tweak the below example for your environment...
+Once you have copied everything to your existing registry or served your own registry, you can install `NeuVector` as normal, with a few modified values to account for the airgapped environment. Please note you may need to adjust the below example for your environment.
 
 ```bash
 # set registry url