[HWORKS-1048] Multi-env documentation (#402)

Author: robzor92

docs/admin/ha-dr/dr.md

@@ -12,7 +12,7 @@ Backing up service/application metrics and services/applications logs are out of
 
 Apache Kafka and OpenSearch are additional services maintaining state. The OpenSearch metadata can be reconstructed from the metadata stored on RonDB.
 
-Apache Kafka is used in Hopsworks to store the in-flight data that is on its way to the online feature store. In the event of a total loss of the cluster, running jobs with inflight data will have to be replayed.
+Apache Kafka is used in Hopsworks to store the in-flight data that is on its way to the online feature store. In the event of a total loss of the cluster, running jobs with in-flight data will have to be replayed.
 
 ### Configuration Backup
 

docs/admin/ldap/configure-server.md

@@ -6,7 +6,7 @@ cluster definition used to deploy your Hopsworks cluster. This tutorial shows an
 server for LDAP and Kerberos integration.
 
 ## Prerequisites
-An accessable LDAP domain. 
+An accessible LDAP domain. 
 A Kerberos Key Distribution Center (KDC) running on the same domain as Hopsworks (Only for Kerberos).
 
 ### Step 1: Server Configuration for LDAP
@@ -43,7 +43,7 @@ Go to the payara admin UI and create a new JNDI external resource. The name of t
   <figcaption>LDAP Resource</figcaption>
 </figure>
 
-This can also be achived by running the bellow asadmin command.
+This can also be achieved by running the below asadmin command.
 
 ```bash
 asadmin create-jndi-resource \

docs/admin/monitoring/services-logs.md

@@ -29,7 +29,7 @@ In the OpenSearch dashboard web application you will see by default all the logs
 
 You can filter the logs of a specific service by searching for the term `service:[service name]`. As shown in the picture below, you can search for the _namenode_ logs by querying `service:namenode`.
 
-Currently only the logs of the following services are collected and indexed: Hopsworks web application (called `domain1` in the log entires), namenodes, resource managers, datanodes, nodemanagers, Kafka brokers, Hive services and RonDB. These are the core component of the platform, additional logs will be added in the future.
+Currently only the logs of the following services are collected and indexed: Hopsworks web application (called `domain1` in the log entries), namenodes, resource managers, datanodes, nodemanagers, Kafka brokers, Hive services and RonDB. These are the core component of the platform, additional logs will be added in the future.
 
 <figure>
   <img src="../../../assets/images/admin/monitoring/services_logs.png" alt="OpenSearch Dashboards with services logs" />

docs/admin/oauth2/create-azure-client.md

@@ -29,7 +29,7 @@ Enter a name for the client such as *hopsworks_oauth_client*. Verify the Support
   </figure>
 </p>
 
-### Step 2: Get the nessary fields for client registration
+### Step 2: Get the necessary fields for client registration
 In the Overview section, copy the *Application (client) ID field*. We will use it in 
 [Identity Provider registration](../create-client) under the name *Client id*.
 

docs/admin/oauth2/create-okta-client.md

@@ -52,7 +52,7 @@ match all groups. See [Group mapping](../create-client/#group-mapping) on how to
     <figcaption>Group claim</figcaption>
   </figure>
 
-### Step 2: Get the nessary fields for client registration
+### Step 2: Get the necessary fields for client registration
 After the application is created go back to _Applications_ and click on the application you just created. Use the
 _Okta domain_ (_Connection URL_), _client id_ and _client secret_ generated for your app in the 
 [Identity Provider registration](../create-client) in Hopsworks.

docs/admin/project.md

@@ -14,7 +14,7 @@ You need to be an administrator on a Hopsworks cluster.
 
 ## Changing project quotas
 
-You can find the Project management page by clicking on your name, in the top right coner of the navigation bar, and choosing _Cluster Settings_ from the dropdown menu and going to the _Project_ tab.
+You can find the Project management page by clicking on your name, in the top right corner of the navigation bar, and choosing _Cluster Settings_ from the dropdown menu and going to the _Project_ tab.
 
 <figure>
   <img src="../../assets/images/admin/projects/project_list.png" alt="Project page" />
@@ -53,7 +53,7 @@ Compute quotas represents the amount of compute a project can use to run Spark a
 
 If the Hopsworks cluster is connected to a Kubernetes cluster, Python jobs, Jupyter notebooks and KServe models are not subject to the compute quota. Currently, Hopsworks does not support defining quotas for compute scheduled on the connected Kubernetes cluster.
 
-By default, the compute quota is disabled. Administrators can change this default by changing the following configuration in the [Condiguration](../admin/variables.md) UI and/or the cluster definition:
+By default, the compute quota is disabled. Administrators can change this default by changing the following configuration in the [Configuration](../admin/variables.md) UI and/or the cluster definition:
 ```
 hopsworks:
     yarn_default_payment_type: [NOLIMIT to disable the quota, PREPAID to enable it]

docs/admin/roleChaining.md

@@ -16,7 +16,7 @@ Before you begin this guide you'll need the following:
 To use role chaining the head node need to be able to impersonate the roles you want to be linked to your project. For this you need to create an instance profile with assume role permissions and attach it to your head node. For more details about the creation of instance profile see the [aws documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2.html). If running in [managed.hopsworks.ai](https://managed.hopsworks.ai) you can also refer to our [getting started guide](../setup_installation/aws/getting_started.md#step-3-creating-instance-profile).
 
 !!!note 
-    To ensure that the Hopsworks users can't use the head node instance profile and impersonate the roles by their own means, you need to ensure that they can't execute code on the head node. This means having all jobs running on worker nodes and using EKS to run jupyter nodebooks.
+    To ensure that the Hopsworks users can't use the head node instance profile and impersonate the roles by their own means, you need to ensure that they can't execute code on the head node. This means having all jobs running on worker nodes and using EKS to run jupyter notebooks.
 
 ```json
 {
@@ -58,7 +58,7 @@ For the instance profile to be able to impersonate the roles you need to configu
 <figcaption>Example trust-policy document.</figcaption>
 
 ### Step 3: Create mappings
-Now that the head node can assume the roles we need to configure Hopsworks to deletegate access to the roles on a project base.
+Now that the head node can assume the roles we need to configure Hopsworks to delegate access to the roles on a project base.
 
 In Hopsworks, click on your name in the top right corner of the navigation bar and choose _Cluster Settings_ from the dropdown menu.
 In the Cluster Settings' _IAM Role Chaining_ tab you can configure the mappings between projects and IAM roles.