docs: helm_chart.mdx (#314)

Updated the documentation to improve readability.

Author: rmarable-flaretx

pages/docs/local/helm_chart.mdx

@@ -3,22 +3,19 @@ title: 🪖 Helm Chart
 description: Instructions for deploying LibreChat on Kubernetes using Helm
 ---
 
-# Deployment a LibreChat Helm Chart
+# Deploy a LibreChat Helm Chart
 
-The following instructions guide you to deploy LibreChat on Kubernetes using Helm.
-
-Note: this method was contributed by the community. If you are familiar with Helm and Kubernetes, use this guide as a reference and adjust to your needs. You can also reference other helm charts made by the community below in the [Community Helm Charts](#community-helm-charts) section.
+Please follow this guidance to deploy LibreChat on Kubernetes using Helm, adjusting as needed for your specific use case. Other Helm charts contributed by the community are listed below in the [Community Helm Charts](#community-helm-charts) section.
 
 ## Prerequisites
 
 * A running Kubernetes cluster
-* `kubectl` installed
-* Helm installed on your local machine
+* _Local_ installations of `kubectl` and Helm
 
 ## Configuration
 
-1. Use the [Credentials Generator](/toolkit/creds_generator) to quickly generate secure values for `CREDS_KEY`, `JWT_SECRET`, `JWT_REFRESH_SECRET` and `MEILI_MASTER_KEY`.
-Place them in a Kubernetes Secret like this (If you want to change the secret name, remember to change it in your helm values):
+1. Use the [Credentials Generator](/toolkit/creds_generator) to generate secure values for `CREDS_KEY`, `JWT_SECRET`, `JWT_REFRESH_SECRET` and `MEILI_MASTER_KEY`.
+Place them in a Kubernetes Secret like this (if you change the secret name, remember to update your Helm values):
 
 ```yaml
 apiVersion: v1
@@ -33,7 +30,7 @@ stringData:
   JWT_REFRESH_SECRET: <generated value>
   MEILI_MASTER_KEY: <generated value>
 ```
-2. Depending on the provider you wanna use, add the respective credentials to the Kubernetes secret as well:
+2. Add credentials for the Kubernetes Secret (dependent on the desired provider):
 
 ```yaml
 apiVersion: v1
@@ -42,32 +39,29 @@ kind: Secret
 
   OPENAI_API_KEY: <your secret value>
 ```
-3. Apply the Secret to the Cluster
-
+3. Apply the Secret to the Cluster:
 
 ## Install Helm Chart
-In the root directory run: 
+In the root directory, run: 
 
 `helm install <deployment-name> helmchart`
 
-Similar to other Helm charts, there exists a [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) that serves two primary functions: it outlines the default settings and indicates which configurations are adjustable.
-
-create a values.yaml file with the values you want to change in comparison to the base values
+Similar to other Helm charts, there exists a [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) that outlines the default settings and indicates which configuration options can be modified.
 
+Create a `values.yaml` file populated with the values you want to modify from the default.
 
-After that you can run the following command: `helm install librechat helmchart --values <values-override-filel>`
-     
+Install the Helm chart: `helm install librechat helmchart --values <values-override-filel>`
 
-## Uninstall Helm Chart
+## Uninstall the Helm Chart
 
-In order to uninstall the Helm Chart simply run: `helm uninstall <deployment-name>`
+To uninstall the Helm Chart: `helm uninstall <deployment-name>`
 
 Example: `helm uninstall librechat`
 
 ## Migrate 1.x -> 2.x
-If you used the chart before version 2.x you may have to change your value structure.
+If you used the chart before version 2.x you may need to update the `value` structure.
 
-1. Move Config to librechat.configEnv
+1. Move Config to librechat.configEnv:
 ```diff
 - env:
 -     ALLOW_EMAIL_LOGIN: "true"
@@ -78,9 +72,9 @@ If you used the chart before version 2.x you may have to change your value struc
 +     ALLOW_EMAIL_LOGIN: "true"
 ```
 
-2. Move all your secret Values to a single Secret as described [Configuration Step 1](#configuration). 
-3. If you still want to use an external MongoDB instance, refer to the [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) of the Chart, deactivate the components accordingly and change the fqdn of the Mongodb Instance. This is recommended if you already have data in your externally managed mongodb instance.
+2. Consolidate all Secret values to a single Secret as described in [Configuration Step 1](#configuration). 
+3. To leverage an external MongoDB instance, refer to the [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) of the Chart, deactivate the components accordingly and change the FQDN of the Mongodb instance. This is recommended if data already exists in this externally managed MongoDB instance.
 
 ## Community Helm Charts
 - [LibreChat Helm Chart by Blue Atlas Helm Charts](https://github.com/bat-bs/helm-charts/tree/main/charts/librechat) # will be depricated soon as its migrated here
-- Example submitted by [@dimaby](https://github.com/dimaby) on GitHub: [PR #2879](https://github.com/danny-avila/LibreChat/pull/2879)
+- Submitted by [@dimaby](https://github.com/dimaby) on GitHub: [PR #2879](https://github.com/danny-avila/LibreChat/pull/2879)