Merge pull request #473 from jasonnovichRunAI/v2.14

grammar and MD corrections

Author: jasonnovichRunAI

docs/admin/researcher-setup/cli-install.md

@@ -1,6 +1,6 @@
 # Install the Run:ai Command-line Interface
 
-The Run:ai Command-line Interface (CLI) is __one__ of the ways for a Researcher to send deep learning workloads, acquire GPU-based containers, list jobs, etc.
+The Run:ai Command-line Interface (CLI) is **one** of the ways for a Researcher to send deep learning workloads, acquire GPU-based containers, list jobs, etc.
 
 The instructions below will guide you through the process of installing the CLI. The Run:ai CLI runs on Mac and Linux. You can run the CLI on Windows by using Docker for Windows. See the end of this document.
 
@@ -11,33 +11,32 @@ When enabled, Researcher authentication requires additional setup when installin
 
 ## Prerequisites
 
-*   When installing the command-line interface, it is worth considering future upgrades:
-     * Install the CLI on a dedicated _Jumpbox_ machine. Researchers will connect to the Jumpbox from which they can submit Run:ai commands
+* When installing the command-line interface, it is worth considering future upgrades:
+     * Install the CLI on a dedicated *Jumpbox* machine. Researchers will connect to the Jumpbox from which they can submit Run:ai commands
      * Install the CLI on a shared directory that is mounted on Researchers' machines.  
-*   A __Kubernetes configuration file__. 
-
+* A **Kubernetes configuration file**.
 
 ## Setup
 
 ### Kubernetes Configuration
 
-*   On the Researcher's root folder, create a directory _.kube_. Copy the Kubernetes configuration file into the directory. Each Researcher should have a __separate copy__ of the configuration file. The Researcher should have _write_ access to the configuration file as it stores user defaults. 
-*   If you choose to locate the file at a different location than `~/.kube/config`, you must create a shell variable to point to the configuration file as follows:
+* In the Researcher's root folder, create a directory *.kube*. Copy the Kubernetes configuration file into the directory. Each Researcher should have a **separate copy** of the configuration file. The Researcher should have *write* access to the configuration file as it stores user defaults.
+* If you choose to locate the file at a different location than `~/.kube/config`, you must create a shell variable to point to the configuration file as follows:
 
 ```
 export KUBECONFIG=<Kubernetes-config-file>
 ```
 
-*   Test the connection by running:
+* Test the connection by running:
 
 ```
 kubectl get nodes
 ```
 
-### Install Run:ai CLI 
+### Install Run:ai CLI
 
 * Go to the Run:ai user interface. On the top right select `Researcher Command Line Interface`.
-* Select `Mac`, `Linux` or `Windows`. 
+* Select `Mac`, `Linux` or `Windows`.
 * Download directly using the button or copy the file to run it on a remote machine
 
 === "Mac or Linux"
@@ -48,7 +47,7 @@ kubectl get nodes
      sudo mv runai /usr/local/bin/runai
      ```
 
-=== "Windows" 
+=== "Windows"
      Rename the downloaded file to have a `.exe` extension and move the file to a folder that is a part of the `PATH`.
 
 !!! Note
@@ -63,7 +62,7 @@ To verify the installation run:
 runai list jobs
 ```
 
-## Install Command Auto-Completion 
+## Install Command Auto-Completion
 
 It is possible to configure your Linux/Mac shell to complete Run:ai CLI commands. This feature works on _bash_ and _zsh_ shells only.
 

docs/home/whats-new-2-14.md

@@ -8,7 +8,7 @@ August 2023
 
 #### Release content
 
-This version contains features and fixes from previous versions. Refer to the prior versions for specific features and fixes. For information about features, functionality, and fixed issues in previous versions see:
+This version contains new features and fixes in addition to the features and fixes from previous versions. For information about features, functionality, and fixed issues in previous versions see:
 
 * [What's new 2.13](whats-new-2-13.md)
 * [What's new 2.12](whats-new-2-12.md)
@@ -24,7 +24,7 @@ TODO Add RBAC old--new conversion table here. -->
 
 ##### Auto delete jobs
 <!-- RUN-8586/RUN-11777 -->
-* We are pleased to announce new functionality in our UI and CLI that provides configuration options which automatically delete jobs after a specified amount of time. Auto-deletion provides more efficient use of resources and makes it easier for researchers to manage their jobs. For more configuration options in the UI, see Auto deletion (Step 9) in [Create a new workspace](../Researcher/user-interface/workspaces/create/workspace-v2.md#create-a-new-workspace). For more information on the CLI flag, see [--auto-deletion-time-after-completion](../Researcher/cli-reference/runai-submit.md).
+* We are pleased to announce new functionality in our UI and CLI that provides configuration options which automatically delete jobs after a specified amount of time. Auto-deletion provides more efficient use of resources and makes it easier for researchers to manage their jobs. For more configuration options in the UI, see *Auto deletion* (Step 9) in [Create a new workspace](../Researcher/user-interface/workspaces/create/workspace-v2.md#create-a-new-workspace). For more information on the CLI flag, see [--auto-deletion-time-after-completion](../Researcher/cli-reference/runai-submit.md).
 
 ##### Multiple service types
 <!-- RUN-10235/RUN-10485  Support multi service types in the CLI submission -->
@@ -47,7 +47,7 @@ TODO Add RBAC old--new conversion table here. -->
 
 ##### Policy improvements
 <!-- RUN-10575/RUN-10579 Add numeric rules in the policy to GPU memory, CPU memory & CPU -->
-* We are pleased to announce increased flexibility when creating policies. The improved flexibility includes the abililty to allocate a `min` and a `max` value for CPU and GPU memory. For configuration information, see [GPU and CPU memory limits](../admin/workloads/policies.md#gpu-and-cpu-memory-limits) in *Configuring policies*.
+* We are pleased to announce increased flexibility when creating policies. The improved flexibility includes the ability to allocate a `min` and a `max` value for CPU and GPU memory. For configuration information, see [GPU and CPU memory limits](../admin/workloads/policies.md#gpu-and-cpu-memory-limits) in *Configuring policies*.
 
 ##### Resource costing
 <!-- RUN-11421/RUN-11508 Consumption report cost and bugs -->