some more changes

Author: jasonnovichRunAI

docs/admin/admin-ui-setup/admin-ui-users.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-The Run:ai UI allows the creation of Run:ai Users. Users are assigned levels of access to the to all aspects of the UI including submitting jobs on the cluster.
+The Run:ai UI allows the creation of Run:ai Users. Users are assigned levels of access to all aspects of the UI including submitting jobs on the cluster.
 
 !!! Tip
     It is possible to connect the Run:ai UI to the organization's directory and use single sign-on (SSO). This allows you to set Run:ai roles for users and groups from the organizational directory. For further information see [single sign-on configuration](../runai-setup/authentication/sso.md).
@@ -21,8 +21,8 @@ To create a new user:
 1. Login to the Run:ai UI at `company-name.run.ai`.
 2. Press the ![Tools and Settings](img/tools-and-settings.svg) icon, then select *Users*.
 3. Press *New user* and enter the user's email address, then press *Create*.
-4. Review the new user information and note the temporary password that has been assigned. You can opt to send the user an introductory email by selecting the checkbox.
-5. When complete, press *Done*.
+4. Review the new user information and note the temporary password that has been assigned. To send the user an introductory email, select the checkbox.
+5. Press *Done* when complete.
 
 ## Assigning access rules to users
 
@@ -31,12 +31,12 @@ Once you have created the users you can assign them *Access rules*. This provide
 To add an *Access rule* to a user:
 
 1. Select the user, then press *Access rules*, then press *+Access rule*.
-2. From the dropdown, select a *Role*.
-3. Press on the ![Scope](../../images/scope-icon.svg) and select a scope for the user.
+2. Select a *Role* from the dropdown.
+3. Press ![Scope](../../images/scope-icon.svg) then select a scope for the user. You can select multiple scopes.
 4. After selecting all the required scopes, press *Save rule*.
-5. If you want to add another rule, use the *+Access rule*.
-6. When all the rules are configured, press *Done*.
+5. To add another rule, use the *+Access rule*.
+6. Press *Done* when all the rules are configured.
 
 ### Roles and permissions
 
-Roles provide a way to group permissions and assign them to either users or user groups. The role identifies the collection of permissions that administrators assign to users or user groups. Permissions define the actions that users can perform on the managed entities. The following table shows the default roles and permissions. For more information on roles, see [Role based access control](../runai-setup/access-control/rbac.md).
+Roles provide a way for administrators to group and identify collections of permissions that administrators assign to [subjects](../runai-setup/access-control/rbac.md#subjects). Permissions define the actions that can be performed on managed entities. The [Roles](../runai-setup/access-control/rbac.md#roles) table shows the default roles and permissions that come with the syste. See [Role based access control](../runai-setup/access-control/rbac.md) for more information.

docs/developer/cluster-api/submit-yaml.md

@@ -106,12 +106,13 @@ spec:
             container: 8000
 ```
 
-1. Possible metrics can be `cpu-utilization`, `latency`, `throughput`, `concurrency`, `gpu-utilization`, `custom`. Different metrics may require additional [installations](../../admin/runai-setup/cluster-setup/cluster-prerequisites.md#inference) at the cluster level. 
+1. Possible metrics can be `cpu-utilization`, `latency`, `throughput`, `concurrency`, `gpu-utilization`, `custom`. Different metrics may require additional [installations](../../admin/runai-setup/cluster-setup/cluster-prerequisites.md#inference) at the cluster level.
 2. Inference requires a port to receive requests.
 
 ## Suspend/Resume Interactive/Training Workload
 
-to suspend trainig
+To suspend training:
+
 ```YAML
 apiVersion: run.ai/v2alpha1
 kind: TrainingWorkload # 
@@ -128,9 +129,8 @@ spec:
   name:
     value: job-1 # 
 ```
-In order to suspend workload set `active` value to `false`
-To reume it back either set `active` value to `true` or remove it entirly. 
-
+In order to suspend the workload, set `active` to `false`.
+To resume the workload, either set `active` to `true` or remove it entirely.
 
 ## See Also
 * To understand how to connect to the inference workload, see [Inference Quickstart](../../Researcher/Walkthroughs/quickstart-inference.md).

mkdocs.yml

@@ -12,11 +12,15 @@ theme:
   logo: images/RUNAI-LOGO-DIGITAL-2C_WP.svg
   features:
     - navigation.tabs
+    - navigation.tabs.sticky
     - search.highlight
     - content.code.annotate
     - content.tabs.link
     - search.suggest
     - content.action.edit
+    - navigation.top
+    - toc.follow
+  #  - toc.integrate 
   icon:
     edit: material/pencil 
     view: material/eye