diff --git a/docs/partials/replicated-cli/_install-docker.mdx b/docs/partials/replicated-cli/_install-docker.mdx
new file mode 100644
index 0000000000..d6f1c5af26
--- /dev/null
+++ b/docs/partials/replicated-cli/_install-docker.mdx
@@ -0,0 +1,36 @@
+:::note
+For Windows users, Replicated recommends using Windows Subsystem for Linux (WSL2) and installing the Replicated using the Linux installations above. See [Linux / Windows Subsystem for Linux (WSL2)](#linux-wsl2).
+:::
+
+Installing in Docker environments requires that you set the `REPLICATED_API_TOKEN` environment variable to authorize the Replicated CLI with an API token. For more information, see [(Optional) Set Environment Variables](#env-var) below.
+
+To install and run the latest Replicated CLI in Docker environments:
+
+1. Generate a service account or user API token in the vendor portal. To create new releases, the token must have `Read/Write` access. See [Generating API Tokens](/vendor/replicated-api-tokens).
+
+1. Get the latest Replicated CLI installation files from the [replicatedhq/replicated repository](https://github.com/replicatedhq/replicated/releases) on GitHub.
+
+    Download and install the files. For simplicity, the usage in the next step is represented assuming that the CLI is downloaded and installed to the desktop.
+
+1. Authorize the Replicated CLI:
+
+     - Through a Docker container:
+
+        ```shell
+        docker run \
+          -e REPLICATED_API_TOKEN=$TOKEN \
+          replicated/vendor-cli --help
+        ```
+        Replace `TOKEN` with your API token.
+
+     - On Windows:
+
+        ```dos
+        docker.exe run \
+          -e REPLICATED_API_TOKEN=%TOKEN% \
+          replicated/vendor-cli --help
+        ```
+
+        Replace `TOKEN` with your API token.
+
+  For more information about the `docker run` command, see [docker run](https://docs.docker.com/engine/reference/commandline/run/) in the Docker documentation. 
\ No newline at end of file
diff --git a/docs/partials/replicated-cli/_install-linux.mdx b/docs/partials/replicated-cli/_install-linux.mdx
new file mode 100644
index 0000000000..16b1fe02dc
--- /dev/null
+++ b/docs/partials/replicated-cli/_install-linux.mdx
@@ -0,0 +1,10 @@
+Run the following command:
+
+    ```shell
+    curl -Ls $(curl -s https://api.github.com/repos/replicatedhq/replicated/releases/latest \
+      | grep "browser_download_url.*linux_amd64.tar.gz" \
+      | cut -d : -f 2,3 \
+      | tr -d \") -o replicated.tar.gz
+    tar xf replicated.tar.gz replicated && rm replicated.tar.gz
+    mv replicated /usr/local/bin/replicated
+    ```
\ No newline at end of file
diff --git a/docs/partials/replicated-cli/_install-mac.mdx b/docs/partials/replicated-cli/_install-mac.mdx
new file mode 100644
index 0000000000..959b25456f
--- /dev/null
+++ b/docs/partials/replicated-cli/_install-mac.mdx
@@ -0,0 +1,18 @@
+Run one of the following commands:
+
+    - With Brew:
+
+      ```shell
+      brew install replicatedhq/replicated/cli
+      ```
+
+    - Without Brew:
+
+      ```shell
+      curl -Ls $(curl -s https://api.github.com/repos/replicatedhq/replicated/releases/latest \
+        | grep "browser_download_url.*darwin_all.tar.gz" \
+        | cut -d : -f 2,3 \
+        | tr -d \") -o replicated.tar.gz
+      tar xf replicated.tar.gz replicated && rm replicated.tar.gz
+      mv replicated /usr/local/bin/replicated
+      ```
\ No newline at end of file
diff --git a/docs/reference/replicated-cli-installing.mdx b/docs/reference/replicated-cli-installing.mdx
index 031b33ab89..0c1a3ed3d1 100644
--- a/docs/reference/replicated-cli-installing.mdx
+++ b/docs/reference/replicated-cli-installing.mdx
@@ -1,4 +1,7 @@
 import Verify from "../partials/replicated-cli/_verify-install.mdx"
+import InstallMac from "../partials/replicated-cli/_install-mac.mdx"
+import InstallLinux from "../partials/replicated-cli/_install-linux.mdx"
+import InstallDocker from "../partials/replicated-cli/_install-docker.mdx"
 import Sudo from "../partials/replicated-cli/_sudo-install.mdx"
 import Login from "../partials/replicated-cli/_login.mdx"
 import Logout from "../partials/replicated-cli/_logout.mdx"
@@ -30,24 +33,7 @@ You can install and run the Replicated CLI in the following environments:
 
 To install and run the latest Replicated CLI on MacOS:
 
-1. Run one of the following commands:
-
-    - With Brew:
-
-      ```shell
-      brew install replicatedhq/replicated/cli
-      ```
-
-    - Without Brew:
-
-      ```shell
-      curl -Ls $(curl -s https://api.github.com/repos/replicatedhq/replicated/releases/latest \
-        | grep "browser_download_url.*darwin_all.tar.gz" \
-        | cut -d : -f 2,3 \
-        | tr -d \") -o replicated.tar.gz
-      tar xf replicated.tar.gz replicated && rm replicated.tar.gz
-      mv replicated /usr/local/bin/replicated
-      ```
+1. <InstallMac/>
 
       <Sudo/>
 
@@ -59,20 +45,13 @@ To install and run the latest Replicated CLI on MacOS:
 
 1. <Logout/>
 
-### Linux
+### Linux / Windows Subsystem for Linux (WSL) {#linux-wsl2}
 
-To install and run the latest Replicated CLI on Linux:
+To install and run the latest Replicated CLI on Linux or Windows Subsystem for Linux (WSL):
 
-1. Run the following command:
+1. For Windows users, first install Linux on Windows using WSL2. See [How to install Linux on Windows with WSL](https://learn.microsoft.com/en-us/windows/wsl/install).
 
-    ```shell
-    curl -Ls $(curl -s https://api.github.com/repos/replicatedhq/replicated/releases/latest \
-      | grep "browser_download_url.*linux_amd64.tar.gz" \
-      | cut -d : -f 2,3 \
-      | tr -d \") -o replicated.tar.gz
-    tar xf replicated.tar.gz replicated && rm replicated.tar.gz
-    mv replicated /usr/local/bin/replicated
-    ```
+1. <InstallLinux/>
 
     <Sudo/>
 
@@ -86,38 +65,7 @@ To install and run the latest Replicated CLI on Linux:
 
 ### Docker / Windows
 
-Installing in Docker environments requires that you set the `REPLICATED_API_TOKEN` environment variable to authorize the Replicated CLI with an API token. For more information, see [(Optional) Set Environment Variables](#env-var) below.
-
-To install and run the latest Replicated CLI in Docker environments:
-
-1. Generate a service account or user API token in the vendor portal. To create new releases, the token must have `Read/Write` access. See [Generating API Tokens](/vendor/replicated-api-tokens).
-
-1. Get the latest Replicated CLI installation files from the [replicatedhq/replicated repository](https://github.com/replicatedhq/replicated/releases) on GitHub.
-
-    Download and install the files. For simplicity, the usage in the next step is represented assuming that the CLI is downloaded and installed to the desktop.
-
-1. Authorize the Replicated CLI:
-
-     - Through a Docker container:
-
-        ```shell
-        docker run \
-          -e REPLICATED_API_TOKEN=$TOKEN \
-          replicated/vendor-cli --help
-        ```
-        Replace `TOKEN` with your API token.
-
-     - On Windows:
-
-        ```dos
-        docker.exe run \
-          -e REPLICATED_API_TOKEN=%TOKEN% \
-          replicated/vendor-cli --help
-        ```
-
-        Replace `TOKEN` with your API token.
-
-  For more information about the `docker run` command, see [docker run](https://docs.docker.com/engine/reference/commandline/run/) in the Docker documentation.  
+<InstallDocker/> 
 
 ## (Optional) Set Environment Variables {#env-var}
 
diff --git a/docs/vendor/environment-setup.mdx b/docs/vendor/environment-setup.mdx
new file mode 100644
index 0000000000..3b2ceb089d
--- /dev/null
+++ b/docs/vendor/environment-setup.mdx
@@ -0,0 +1,287 @@
+import Requirements from "../partials/embedded-cluster/_requirements.mdx"
+import Verify from "../partials/replicated-cli/_verify-install.mdx"
+import InstallMac from "../partials/replicated-cli/_install-mac.mdx"
+import InstallLinux from "../partials/replicated-cli/_install-linux.mdx"
+import InstallDocker from "../partials/replicated-cli/_install-docker.mdx"
+import Sudo from "../partials/replicated-cli/_sudo-install.mdx"
+import Login from "../partials/replicated-cli/_login.mdx"
+import Logout from "../partials/replicated-cli/_logout.mdx"
+import AuthToken from "../partials/replicated-cli/_authorize-with-token-note.mdx"
+
+# Set Up Your Environment
+
+This topic describes how to set up your environment to get started with the Replicated Platform. It includes information about installing the required tools on your local workstation as well as creating development environments for testing installation and upgrade scenarios for your application.
+
+## Set Up Your Local Workstation {#local}
+
+This section lists the tools that you need to install on your local workstation to manage applications, releases, customers, and more with the Replicated Platform.
+
+### Install kubectl
+
+kubectl is the Kubernetes command line tool. You will use kubectl to communicate with the clusters that you create with the Replicated Compatibility Matrix, and when testing and troubleshooting installations in existing clusters. For more information about kubectl, see [Command line tool (kubectl)](https://kubernetes.io/docs/reference/kubectl/) in the Kubernetes documentation.
+
+#### Mac
+
+To install kubectl on Mac, do one of the following:
+
+* Install with Homebrew:
+    ```bash
+    brew install kubectl
+    ```
+* Install using curl:
+
+    ```bash
+    curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl"
+    chmod +x ./kubectl
+    sudo mv ./kubectl /usr/local/bin/kubectl
+    ```
+
+#### Linux
+
+To install kubectl on Linux, do one of the following:
+
+* Install using curl:
+
+    ```bash
+    curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
+    chmod +x ./kubectl
+    sudo mv ./kubectl /usr/local/bin/kubectl
+    ```
+
+* Install with a package manager (Ubuntu/Debain):
+
+    ```bash
+    sudo apt-get update
+    sudo apt-get install -y kubectl
+    ```
+
+* Install with a package manager (CentOS/RHEL/Fedora):
+
+    ```bash
+    sudo yum install -y kubectl
+    ```
+
+### Install Helm
+
+The Helm CLI is the tool for interacting with Helm and managing charts. Replicated recommends that all applications distributed with the Replicated Platform are packaged with Helm. Helm charts distributed with Replicated can also be installed in customer environments using Helm. Installing the Helm CLI on your workstation is important for being able to test and troubleshoot installations with Helm.
+
+For more information, see [Installing Helm](https://helm.sh/docs/intro/install/) in the Helm documentation.
+
+#### Mac
+
+To install the Helm CLI on Mac, do one of the following:
+
+* Install with Homebrew:
+
+    ```bash
+    brew install helm
+    ```
+
+* Install using curl:
+
+    ```bash
+    curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
+    ```
+
+#### Linux
+
+To install the Helm CLI on Linux:
+
+```bash
+curl -LO https://get.helm.sh/helm-v3.12.0-linux-amd64.tar.gz
+tar -zxvf helm-v3.12.0-linux-amd64.tar.gz
+sudo mv linux-amd64/helm /usr/local/bin/helm
+```
+
+###  Install and Authorize the Replicated CLI
+
+The Replicated CLI is the primary interface for the Replicated Platform. With the Replicated CLI, you can create and manage applications, releases, channels, customers, and more. You also use the Replicated CLI to create clusters with the Compatibility Matrix.
+
+After installing, you can authorize the Replicated CLI by logging in to your Replicated vendor account through the `replicated login` command.
+
+For more information about installing and authorizing the Replicated CLI, see [Install the Replicated CLI](/reference/replicated-cli-installing).
+
+#### Mac
+
+To install and run the latest Replicated CLI on MacOS:
+
+1. <InstallMac/>
+
+      <Sudo/>
+
+1. <Verify/>
+
+1. <Login/>
+
+   <AuthToken/>
+
+1. <Logout/>
+
+#### Linux / Windows Subsystem for Linux (WSL2) {#linux-wsl2}
+
+To install and run the latest Replicated CLI on Linux or Windows Subsystem for Linux (WSL2):
+
+1. For Windows users, first install Linux on Windows using WSL2. See [How to install Linux on Windows with WSL](https://learn.microsoft.com/en-us/windows/wsl/install).
+
+1. <InstallLinux/>
+
+    <Sudo/>
+
+1. <Verify/>
+
+1. <Login/>
+
+   <AuthToken/>
+
+1. <Logout/>
+
+#### Docker / Windows
+
+<InstallDocker/> 
+
+### Install the Preflight and Support Bundle Plugins
+
+The preflight and support-bundle plugins available through the open source Troubleshoot project provide important troubleshooting tools for your customers, allowing them to run preflight checks and collect support bundles. For more information, see [About Preflight Checks and Support Bundles](/vendor/preflight-support-bundle-about).
+
+These instructions show you how to install the Troubleshoot plugins using Krew. For more information about installing the preflight and support-bundle plugins, including other installation options, see [Getting Started](https://troubleshoot.sh/docs/) in the Troubleshoot documentation.
+
+To install the preflight and support-bundle plugins:
+
+1. Install Krew:
+
+    * Mac: 
+      ```bash
+      brew install krew
+      ```
+    * Other operating systems:
+      ```bash
+      (
+        set -x; cd "$(mktemp -d)" &&
+        OS="$(uname | tr '[:upper:]' '[:lower:]')" &&
+        ARCH="$(uname -m | sed -e 's/x86_64/amd64/' -e 's/\(arm\)\(64\)\?.*/\1\2/' -e 's/aarch64$/arm64/')" &&
+        KREW="krew-${OS}_${ARCH}" &&
+        curl -fsSLO "https://github.com/kubernetes-sigs/krew/releases/latest/download/${KREW}.tar.gz" &&
+        tar zxvf "${KREW}.tar.gz" &&
+        ./"${KREW}" install krew
+      )
+      ``` 
+
+1. After installing, add the krew binary directory to your PATH:
+
+    ```bash
+    echo 'export PATH="${KREW_ROOT:-$HOME/.krew}/bin:$PATH"' >> ~/.bashrc
+    source ~/.bashrc
+    ```
+
+1. Run the following commands:
+
+   ```bash
+   kubectl krew install preflight
+   kubectl krew install support-bundle
+   ```
+
+### Install sbctl
+
+sbctl is a command-line tool that makes it easier to troubleshoot an installation using a support bundle. With sbctl, you provide a support bundle that was collected in a cluster. sbctl then generates a kubeconfig file based on the contents of the support bundle an opens an interactive shell. In the sbctl shell, you can run kubectl commands to interact with a representation of the state of the cluster when the support bundle was collected.
+
+For more information, see the [sbctl](https://github.com/replicatedhq/sbctl) repository in GitHub.
+
+To install sbctl, run one of the following commands:
+
+* macOS Intel systems:
+
+    ```bash
+    curl -LO https://github.com/replicatedhq/sbctl/releases/latest/download/sbctl_darwin_amd64.tar.gz
+    tar -xzf sbctl_darwin_amd64.tar.gz -C /tmp sbctl
+    rm -f sbctl_darwin_amd64.tar.gz
+    sudo mv /tmp/sbctl /usr/local/bin/
+    ```
+
+* macOS Apple Silicon:
+    ```bash
+    curl -LO https://github.com/replicatedhq/sbctl/releases/latest/download/sbctl_darwin_arm64.tar.gz
+    tar -xzf sbctl_darwin_arm64.tar.gz -C /tmp sbctl
+    rm -f sbctl_darwin_arm64.tar.gz
+    sudo mv /tmp/sbctl /usr/local/bin/
+    ```
+
+* Linux x86_64:
+    ```bash
+    curl -LO https://github.com/replicatedhq/sbctl/releases/latest/download/sbctl_linux_amd64.tar.gz
+    tar -xzf sbctl_linux_amd64.tar.gz -C /tmp sbctl
+    rm -f sbctl_linux_amd64.tar.gz
+    sudo mv /tmp/sbctl /usr/local/bin/
+    ```
+
+* Linux ARM64:
+    ```bash
+    curl -LO https://github.com/replicatedhq/sbctl/releases/latest/download/sbctl_linux_arm64.tar.gz
+    tar -xzf sbctl_linux_arm64.tar.gz -C /tmp sbctl
+    rm -f sbctl_linux_arm64.tar.gz
+    sudo mv /tmp/sbctl /usr/local/bin/
+    ```
+
+### (Recommended) Install Data Processing Tools
+
+Replicated recommends that you install the following tools for parsing and manipulating JSON and YAML data:
+* [jq](https://jqlang.org/) for JSON processing
+* [yq](https://mikefarah.gitbook.io/yq/) for YAML manipulation
+
+These tools are useful when working with Kubernetes and Replicated configurations to reduce complex data manipulation tasks from multi-step processes into single commands, simplifying your development workflow.
+
+* To install jq, run one of the following commands:
+
+    * macOS:
+      ```bash
+      brew install jq
+      ```
+    * Ubuntu/Debian:
+      ```bash
+      sudo apt-get install jq
+      ```
+    * CentOS/RHEL/Fedora"   
+      ```bash
+      sudo yum install jq
+      ```
+    * Direct download:  
+      ```bash
+      curl -LO https://github.com/stedolan/jq/releases/latest/download/jq-linux64
+      chmod +x jq-linux64
+      sudo mv jq-linux64 /usr/local/bin/jq
+      ```
+
+* To install yq, run one of the following commands:
+    * macOS:
+      ```bash
+      brew install yq
+      ```
+    * Linux:
+      ```bash
+      curl -LO https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64
+      chmod +x yq_linux_amd64
+      sudo mv yq_linux_amd64 /usr/local/bin/yq
+      ```
+    * Go install:
+      ```bash
+      go install github.com/mikefarah/yq/v4@latest
+      ```
+
+## Set Up Development Environments for Testing {#dev}
+
+Testing your releases is an important part of the commercial software distribution lifecycle. Replicated recommends that you have access to a virtual machine (VM) and a cluster where you can install your application releases for testing.
+
+### About Creating a VM
+
+You need access to a VM to test installations and updates with the Replicated Embedded Cluster installer. For more information about Embedded Cluster, see [Embedded Cluster Overview](/vendor/embedded-overview).
+
+Your VM must meet the following requirements to install with Embedded Cluster:
+
+<Requirements/>
+
+### About Creating a Cluster
+
+To test installations with Helm, you need kubectl access to a cluster.
+
+You can use any cloud provider or tool that you prefer to create a cluster, such as [Replicated Compatibility Matrix](/vendor/testing-how-to), Google Kubernetes Engine (GKE), or minikube.
+
+For information about how to create a cluster with Compatibility Matrix, see [Prerequisites](/vendor/testing-how-to#prerequisites) and [Create Clusters](/vendor/testing-how-to#create-clusters) in _Use Compatibility Matrix_.
\ No newline at end of file
diff --git a/docs/vendor/replicated-onboarding.mdx b/docs/vendor/replicated-onboarding.mdx
index a3cc62e120..208b2ea56b 100644
--- a/docs/vendor/replicated-onboarding.mdx
+++ b/docs/vendor/replicated-onboarding.mdx
@@ -21,11 +21,9 @@ The following are some best practices and recommendations for successfully onboa
 
 * When integrating new Replicated features with an application, make changes in small iterations and test frequently by installing or upgrading the application in a development environment. This will help you to more easily identify issues and troubleshoot. This onboarding workflow will guide you through the process of integrating features in small iterations.
 
-* Use the Replicated CLI to create and manage your application and releases. Getting familiar with the Replicated CLI will also help later on when integrating Replicated workflows into your CI/CD pipelines. For more information, see [Install the Replicated CLI](/reference/replicated-cli-installing).
+* Use the Replicated CLI to create and manage your application and releases. Getting familiar with the Replicated CLI will also help later on when integrating Replicated workflows into your CI/CD pipelines.
 
-* These onboarding tasks assume that you will test the installation of each release on a VM with the Replicated Embedded Cluster installer _and_ in a cluster with the Replicated KOTS installer. If you do not intend to offer existing cluster installations with KOTS (for example, if you intend to support only Embedded Cluster and Helm installations for your users), then can choose to test with Embedded Cluster only.
-
-* Ask for help from the Replicated community. For more information, see [Get Help from the Community](#community) below.
+* These onboarding tasks show you how to test the installation of each release on a VM with the Replicated Embedded Cluster installer _and_ in a cluster with the Replicated KOTS installer. If you do not intend to offer existing cluster installations with KOTS, then can choose to test with Embedded Cluster only.
 
 ### Getting Help from the Community {#community}
 
@@ -35,27 +33,27 @@ Before posting in the community site, use the search to find existing knowledge
 
 To search and participate in the Replicated community, see https://community.replicated.com/.
 
-### Prerequisites
+## Prerequisites
 
 * Create an account in the Vendor Portal. You can either create a new team or join an existing team. For more information, see [Create a Vendor Account](vendor-portal-creating-account).
 
-* Install the Replicated CLI. See [Install the Replicated CLI](/reference/replicated-cli-installing).
+* Set up your local workstation with the required toolkit for working with the Replicated Platform. See [Set Up Your Local Workstation](/vendor/environment-setup#local).
 
-* Complete a basic quick start workflow to create an application with a sample Helm chart and then promote and install releases in a development environment. This helps you get familiar with the process of creating, installing, and updating releases in the Replicated Platform. See [Replicated Quick Start](/vendor/quick-start).
+* Set up a VM. You will use this VM to test installing and updating with the Replicated Embedded Cluster installer throughout the main onboarding tasks.
 
-* Ensure that you have access to a VM that meets the requirements for the Replicated Embedded Cluster installer. You will use this VM to test installation with Embedded Cluster.
+    The VM that you create must meet the following requirements for Embedded Cluster:
 
-  Embedded Cluster has the following requirements:
+    <Requirements/>
 
-  <Requirements/>
+* (Optional) Create a Kubernetes cluster for testing Helm installations and/or existing cluster installations with Replicated KOTS. For information about how to create a cluster, see [Create a Kubernetes Cluster](/vendor/environment-setup#create-a-kubernetes-cluster) in _Set Up Your Environment_.
 
-* (Optional) Ensure that you have kubectl access to a Kubernetes cluster. You will use this cluster to test installation with KOTS. If you do not intend to offer existing cluster installations with KOTS (for example, if you intend to support only Embedded Cluster and Helm installations for your users), then you do not need access to a cluster for the main onboarding tasks.
+    If you do _not_ intend to support existing cluster KOTS installations, you can wait to create this cluster until you begin the [Next Steps > Add Support for Helm Installations](/vendor/replicated-onboarding#add-support-for-helm-installations) task.
 
-  You can use any cloud provider or tool that you prefer to create a cluster, such as [Replicated Compatibility Matrix](/vendor/testing-how-to), Google Kubernetes Engine (GKE), or minikube. 
+* Complete a basic quick start workflow to create an application with a sample Helm chart and then promote and install releases in a development environment. This helps you get familiar with the process of creating, installing, and updating releases in the Replicated Platform. See [Replicated Quick Start](/vendor/quick-start).
 
 ## Onboard
 
-Complete the tasks in this section to onboard your application. When you are done, you can continue to [Next Steps](#next-steps) to integrate other Replicated features with your application.
+Complete the tasks in this section to onboard your application to the Replicated Platform, with support for . When you are done, you can continue to [Next Steps](#next-steps) to integrate other Replicated features with your application.
 
 ### Task 1: Create An Application
 
@@ -416,7 +414,7 @@ After completing the main onboarding tasks, Replicated recommends that you also
 
 ### Add Support for Helm Installations
 
-Existing KOTS releases that include one or more Helm charts can be installed with the Helm CLI; it is not necessary to create and manage separate releases or channels for each installation method.
+Existing releases that include one or more Helm charts can be installed with the Helm CLI; it is not necessary to create and manage separate releases or channels for each installation method.
 
 To enable Helm installations for Helm charts distributed with Replicated, the only extra step is to add a Secret to your chart to authenticate with the Replicated proxy registry.  
 
@@ -436,7 +434,9 @@ To support and test Helm installations:
 
 1. Add the `.tgz` file to a release. For more information, see [Manage Releases with the Vendor Portal](releases-creating-releases) or [Managing Releases with the CLI](releases-creating-cli).
 
-1. Install the release in a cluster with the Helm CLI to test your changes. For more information, see [Install with Helm](/vendor/install-with-helm).
+1. Create or get kubectl access to a cluster to test the installation. See [Create a Kubernetes Cluster](/vendor/environment-setup#create-a-kubernetes-cluster) in _Set Up Your Environment_.
+
+1. In the cluster, istall the release with Helm to test your changes. For more information, see [Install with Helm](/vendor/install-with-helm).
 
 ### Add Support for Air Gap Installations
 
diff --git a/sidebars.js b/sidebars.js
index e1175fa232..ec652660b4 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -38,6 +38,7 @@ const sidebars = {
     'intro-replicated',
     'vendor/kots-faq',
     'vendor/quick-start',
+    'vendor/environment-setup',
     'vendor/replicated-onboarding',
     // {
     //   type: 'category',