deploy: fa7dca0

rhods-admin/1.33/chapter1/dependencies-install-web-console.html

@@ -143,7 +143,7 @@ <h1 class="page">Installing Dependencies Using the Web Console</h1>
 <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph">
-<p>As described in the <a href="install-general-info.html" class="xref page">General Information about Installation</a> section you may need to install other operators depending on the components and features of OpenShift AI you want to use.  This section will discuss installing and configuring those components.</p>
+<p>As described in the <a href="install-general-info.html" class="xref page">General Information about Installation</a> section, you may need to install other operators depending on the components and features of OpenShift AI you want to use.  This section will discuss about installing and configuring those components.</p>
 </div>
 <div class="paragraph">
 <p>It is generally recommended to install any dependent operators prior to installing the <strong>Red&#160;Hat OpenShift AI</strong> operator.</p>
@@ -237,7 +237,7 @@ <h3 id="_lab_installation_of_the_redhat_openshift_pipelines_operator"><a class="
 <i class="fa icon-tip" title="Tip"></i>
 </td>
 <td class="content">
-For assistance installing OpenShift Pipelines from YAML or via ArgoCD, refer to examples found in the <a href="https://github.com/redhat-cop/gitops-catalog/tree/main/openshift-pipelines-operator">redhat-cop/gitops-catalog/openshift-pipelines-operator</a> GitHub repo.
+For assistance in installing OpenShift Pipelines from YAML or via ArgoCD, refer to examples found in the <a href="https://github.com/redhat-cop/gitops-catalog/tree/main/openshift-pipelines-operator">redhat-cop/gitops-catalog/openshift-pipelines-operator</a> GitHub repo.
 </td>
 </tr>
 </table>
@@ -264,7 +264,7 @@ <h2 id="_lab_installation_of_gpu_dependencies"><a class="anchor" href="#_lab_ins
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-<strong>Node Feature Discovery</strong> and the <strong>NVIDIA GPU Operator</strong> can both be installed in a cluster that does not have a node with a GPU.  This can be helpful when you plan to add GPUs at a later date.  If a GPU is not present in the cluster the Dashboard will not present the user an option to deploy using a GPU.
+<strong>Node Feature Discovery</strong> and the <strong>NVIDIA GPU Operator</strong> can both be installed in a cluster that does not have a node with a GPU.  This can be helpful when you plan to add GPUs at a later date.  If a GPU is not present in the cluster, the Dashboard will not present the user an option to deploy using a GPU.
 </td>
 </tr>
 </table>
@@ -370,7 +370,7 @@ <h3 id="_demo_installation_of_the_node_feature_discovery_operator"><a class="anc
 <i class="fa icon-tip" title="Tip"></i>
 </td>
 <td class="content">
-For assistance installing the Node Feature Discovery Operator from YAML or via ArgoCD, refer to examples found in the <a href="https://github.com/redhat-cop/gitops-catalog/tree/main/nfd">redhat-cop/gitops-catalog/nfd</a> GitHub repo.
+For assistance in installing the Node Feature Discovery Operator from YAML or via ArgoCD, refer to examples found in the <a href="https://github.com/redhat-cop/gitops-catalog/tree/main/nfd">redhat-cop/gitops-catalog/nfd</a> GitHub repo.
 </td>
 </tr>
 </table>

rhods-admin/1.33/chapter1/uninstalling-rhods.html

@@ -157,7 +157,7 @@ <h2 id="demo-rhods"><a class="anchor" href="#demo-rhods"></a>Demo: Uninstalling
 <i class="fa icon-warning" title="Warning"></i>
 </td>
 <td class="content">
-These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the installed version of the product in the hands on labs in the course.
+These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the installed version of the product in the hands-on labs in the course.
 </td>
 </tr>
 </table>
@@ -177,7 +177,7 @@ <h2 id="demo-rhods"><a class="anchor" href="#demo-rhods"></a>Demo: Uninstalling
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p>Log in to Red&#160; OpenShift web console using a user which has the <em>cluster-admin</em> role assigned.</p>
+<p>Log in to Red&#160;Hat OpenShift web console using a user which has the <em>cluster-admin</em> role assigned.</p>
 </li>
 <li>
 <p>Delete the DataScienceCluster object.</p>
@@ -213,7 +213,7 @@ <h2 id="demo-rhods"><a class="anchor" href="#demo-rhods"></a>Demo: Uninstalling
 <div class="title">Figure 2. Delete DSCI Resource</div>
 </div>
 <div class="paragraph">
-<p>alternatively you can delete the <strong>DCSI</strong> objects from the CLI.</p>
+<p>Alternatively you can delete the <strong>DCSI</strong> objects from the CLI.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -268,7 +268,7 @@ <h2 id="demo-rhods"><a class="anchor" href="#demo-rhods"></a>Demo: Uninstalling
 <li>
 <p>Delete the namespaces that the Operator created during
 installation. They are labeled with label <em>opendatahub.io/generated-namespace=true</em>.
-Deleting namespace <em>rhods-notebooks</em> leads to Persistent Volume Claims (PVC) being used by Workbench get deleted as well.</p>
+Deleting namespace <em>rhods-notebooks</em> leads to Persistent Volume Claims (PVC) being used by Workbench getting deleted as well.</p>
 <div class="paragraph">
 <p>Navigate to <strong>Administration</strong> &#8594; <strong>Namespaces</strong>, filter the namespaces using the label <em>opendatahub.io/generated-namespace=true</em> and delete them.</p>
 </div>
@@ -317,7 +317,7 @@ <h2 id="_uninstalling_the_redhat_openshift_ai_dependencies"><a class="anchor" hr
 <div class="sectionbody">
 <div class="paragraph">
 <p>If you have installed some dependencies you can remove them as long as they are not used by other deployments.
-The following demonstration shows uninstallation of the <strong>Red&#160;Hat OpenShift Pipelines</strong> operator</p>
+The following demonstration shows uninstallation of the <strong>Red&#160;Hat OpenShift Pipelines</strong> operator.</p>
 </div>
 <div class="sect2">
 <h3 id="demo-pipelines"><a class="anchor" href="#demo-pipelines"></a>Demo: Uninstallation of the <strong>Red&#160;Hat OpenShift Pipelines</strong> operator</h3>
@@ -338,7 +338,7 @@ <h3 id="demo-pipelines"><a class="anchor" href="#demo-pipelines"></a>Demo: Unins
 </div>
 </li>
 <li>
-<p>In the pop-up window scroll down, check <strong>Delete all operand instances for this operator</strong> and click on <strong>Uninstall</strong></p>
+<p>In the pop-up window scroll down, check <strong>Delete all operand instances for this operator</strong> and click on <strong>Uninstall</strong>.</p>
 <div class="imageblock">
 <div class="content">
 <img src="_images/piplines-uninstall-confirm.png" alt="piplines uninstall confirm" width="800">

rhods-admin/1.33/chapter1/upgrading-rhods.html

@@ -146,7 +146,7 @@ <h1 class="page">Upgrading Red&#160;Hat OpenShift AI</h1>
 <p>Red Hat OpenShift AI upgrades are handled by the <strong>Red&#160;Hat OpenShift AI</strong> operator.</p>
 </div>
 <div class="paragraph">
-<p>When an upgrade is available <strong>OLM</strong> creates an <strong>Installplan</strong> for the new version.</p>
+<p>When an upgrade is available, <strong>OLM</strong> creates an <strong>Installplan</strong> for the new version.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -169,7 +169,7 @@ <h1 class="page">Upgrading Red&#160;Hat OpenShift AI</h1>
 </table>
 </div>
 <div class="paragraph">
-<p>Installplan is approved either automatically when a new version is available without user&#8217;s intervention or requires a manual approval. Whether the approval is automatic or manual depends on the value of the <strong>installPlanApproval</strong> attribute of the operator&#8217;s subscription. When it is set to <em>Automatic</em> the <strong>installplan</strong> is approved automatically and installation starts without user&#8217;s intervention. <em>Manual</em> value requires a manual approval.</p>
+<p>Installplan is approved either automatically when a new version is available without user&#8217;s intervention or requires a manual approval. Whether the approval is automatic or manual, depends on the value of the <strong>installPlanApproval</strong> attribute of the operator&#8217;s subscription. When it is set to <em>Automatic</em> the <strong>installplan</strong> is approved automatically and installation starts without user&#8217;s intervention. <em>Manual</em> value requires a manual approval.</p>
 </div>
 <div class="paragraph">
 <p>Approvals can be set from the web console as well as from the CLI.</p>
@@ -189,7 +189,7 @@ <h2 id="_demo_upgrading_redhat_openshift_ai"><a class="anchor" href="#_demo_upgr
 <i class="fa icon-warning" title="Warning"></i>
 </td>
 <td class="content">
-These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the <em>stable</em> version of the product in the hands on labs in the course.
+These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the <em>stable</em> version of the product in the hands-on labs in the course.
 </td>
 </tr>
 </table>

rhods-admin/1.33/chapter2/resources.html

@@ -151,7 +151,7 @@ <h1 class="page">Managing Resources</h1>
 <h2 id="_kubernetes_resources"><a class="anchor" href="#_kubernetes_resources"></a>Kubernetes Resources</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The majority of actions taken in the OpenShift AI will create a kubernetes object based on that action.  This section will discussion the different components supported by OpenShift AI and the different resources they create or interact with.</p>
+<p>The majority of actions taken in the OpenShift AI will create a kubernetes object based on that action.  This section will discuss the different components supported by OpenShift AI and the different resources they create or interact with.</p>
 </div>
 <div class="sect2">
 <h3 id="_data_science_projects"><a class="anchor" href="#_data_science_projects"></a>Data Science Projects</h3>
@@ -175,7 +175,7 @@ <h3 id="_data_science_projects"><a class="anchor" href="#_data_science_projects"
 <td class="tableblock halign-left valign-top"><p class="tableblock">Data Science Project</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">projects.project.openshift.io</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">No</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A Data Science Project is synonym with an OpenShift Project or a Namespace.  See the users section for more information on how to create and manage Data Science Projects</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A Data Science Project is synonym with an OpenShift Project or a Namespace.  See the users section for more information on how to create and manage Data Science Projects.</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Users</p></td>
@@ -397,7 +397,7 @@ <h2 id="_configuring_idle_notebook_culling"><a class="anchor" href="#_configurin
 <h2 id="_managing_workbench_and_model_server_sizes"><a class="anchor" href="#_managing_workbench_and_model_server_sizes"></a>Managing Workbench and Model Server Sizes</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>When launching Workbenches or Model Servers from the Dashboard, users are presented with several default sizes they can select from.  The default options may not suit your organizations needs</p>
+<p>When launching Workbenches or Model Servers from the Dashboard, users are presented with several default sizes they can select from.  The default options may not suit your organizations needs.</p>
 </div>
 <div class="listingblock">
 <div class="content">

rhods-admin/1.33/chapter2/users.html

@@ -237,7 +237,7 @@ <h2 id="_updating_default_user_permissions"><a class="anchor" href="#_updating_d
 </td>
 <td class="content">
 <div class="paragraph">
-<p>It is highly recommended that dedicated admin users are configured for OpenShift AI and that organizations do not rely on the <code>cluster-admin</code> role for exclusive permissions to admin configurations of OpenShift AI.  Dedicated Admin users should be added to the existing <code>rhods-admins</code> group, or another group which already contains the correct users should be configured in lieu of the <code>rhods-admins</code> group.</p>
+<p>It is highly recommended that dedicated admin users are configured for OpenShift AI and that organizations do not rely on the <code>cluster-admin</code> role for exclusive permissions to admin configurations of OpenShift AI.  Dedicated Admin users should be added to the existing <code>rhods-admins</code> group, or another group which already contains the correct users that should be configured in lieu of the <code>rhods-admins</code> group.</p>
 </div>
 </td>
 </tr>
@@ -254,10 +254,10 @@ <h2 id="_updating_default_user_permissions"><a class="anchor" href="#_updating_d
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Updating the access in the <code>User and group settings</code> in the Dashboard will only impact a users abilities to access the Dashboard, and will not impact any permissions granted by regular Kubernetes based RBAC.</p>
+<p>Updating the access in the <code>User and group settings</code> in the Dashboard will only impact a user&#8217;s abilities to access the Dashboard, and will not impact any permissions granted by regular Kubernetes based RBAC.</p>
 </div>
 <div class="paragraph">
-<p>For example, if the normal user group is updated to only allow specific users to access the Dashboard, and a user that is not part of that group has admin may still have the ability to create Data Science related objects such as Notebooks, Data Science Pipelines, or Model Servers in a namespace they have permission in using the associated k8s objects without the UI.</p>
+<p>For example, if the normal user group is updated to only allow specific users to access the Dashboard, and a user that is not part of that group as admin may still have the ability to create Data Science related objects such as Notebooks, Data Science Pipelines, or Model Servers in a namespace they have permission in using the associated k8s objects without the UI.</p>
 </div>
 </td>
 </tr>

rhods-admin/1.33/chapter3/custom.html

@@ -154,7 +154,7 @@ <h2 id="_image_source_and_pre_built_images"><a class="anchor" href="#_image_sour
 <p>The default OpenShift AI notebook images can be found in the <a href="https://github.com/red-hat-data-services/notebooks">Default OpenShift AI notebooks</a> repository. This repository contains the source code, pre-built images, and examples to help you create your own image.</p>
 </div>
 <div class="paragraph">
-<p>Additional images are available at the ODH contributions repository (<a href="https://github.com/opendatahub-io-contrib/workbench-images">opendatahub-io-contrib/workbench-images</a>) This is a place to source additional images, as well as a great resource for best practices for building custom images. Workbench and runtime images are available as well as a script to generate custom images (<a href="https://github.com/opendatahub-io-contrib/workbench-images#building-an-image" class="bare">https://github.com/opendatahub-io-contrib/workbench-images#building-an-image</a>)</p>
+<p>Additional images are available at the ODH contributions repository (<a href="https://github.com/opendatahub-io-contrib/workbench-images">opendatahub-io-contrib/workbench-images</a>). This is a place to source additional images, as well as a great resource for best practices for building custom images. Workbench and runtime images are available as well as a script to generate custom images (<a href="https://github.com/opendatahub-io-contrib/workbench-images#building-an-image" class="bare">https://github.com/opendatahub-io-contrib/workbench-images#building-an-image</a>).</p>
 </div>
 </div>
 </div>

rhods-admin/1.33/chapter3/importcustom.html

@@ -152,7 +152,7 @@ <h2 id="_import_the_notebook_image"><a class="anchor" href="#_import_the_noteboo
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p>Before we import the image into OpenShif AI we need to set the quay repository we just created to public. In a browser login to quay.io and go to the <strong>rhods-admin-custom-image</strong> repository. Select the <strong>Settings</strong> gear icon.</p>
+<p>Before we import the image into OpenShif AI we need to set the quay repository we just created to public. In a browser, login to quay.io and go to the <strong>rhods-admin-custom-image</strong> repository. Select the <strong>Settings</strong> gear icon.</p>
 <div class="imageblock">
 <div class="content">
 <img src="_images/quaySettings.png" alt="Quay Repository Settings">

rhods-admin/1.33/chapter3/index.html

@@ -151,7 +151,7 @@ <h1 class="page">Building Custom Notebook Images</h1>
 <p>Create custom notebook images</p>
 </li>
 <li>
-<p>How to import custom notebook images into OpenShift AI</p>
+<p>Import custom notebook images into OpenShift AI</p>
 </li>
 </ul>
 </div>

rhods-admin/1.33/index.html

@@ -416,10 +416,10 @@ <h2 id="_prerequisites"><a class="anchor" href="#_prerequisites"></a>Prerequisit
 <p>Basic knowledge of OpenShift (or Kubernetes) administration</p>
 </li>
 <li>
-<p>Building and deploying container images</p>
+<p>Ability to build and deploy container images</p>
 </li>
 <li>
-<p>OpenShift User and Role administration</p>
+<p>Knowledge of OpenShift User and Role administration</p>
 </li>
 <li>
 <p>Basic knowledge of AWS EC2 and S3 services</p>
@@ -437,19 +437,19 @@ <h2 id="_objectives"><a class="anchor" href="#_objectives"></a>Objectives</h2>
 <div class="ulist">
 <ul>
 <li>
-<p>Installing RedHat OpenShift AI using the web console and CLI</p>
+<p>Install RedHat OpenShift AI using the web console and CLI</p>
 </li>
 <li>
-<p>Upgrading RedHat OpenShift AI components</p>
+<p>Upgrade RedHat OpenShift AI components</p>
 </li>
 <li>
-<p>Managing RedHat OpenShift AI users and controlling access</p>
+<p>Manage RedHat OpenShift AI users and controlling access</p>
 </li>
 <li>
-<p>Enabling GPU support in RedHat OpenShift AI</p>
+<p>Enable GPU support in RedHat OpenShift AI</p>
 </li>
 <li>
-<p>Stopping idle notebooks</p>
+<p>Stop idle notebooks</p>
 </li>
 <li>
 <p>Create and configure a custom notebook image</p>