Deployed a5b45ba to task-add-updates-for-tenant-crud-mto-docs-6924 wi…

…th MkDocs 1.6.1 and mike 2.1.3

task-add-updates-for-tenant-crud-mto-docs-6924/how-to-guides/crud/tenant-crud-workflow.html

@@ -4216,7 +4216,7 @@ <h3 class="dropdown-content-column-title">Open Source</h3>
 <h1 id="tenant">Tenant<a class="headerlink" href="#tenant" title="Permanent link">#</a></h1>
 <h2 id="create">Create<a class="headerlink" href="#create" title="Permanent link">#</a></h2>
 <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">#</a></h2>
-<p>The tenant creation process involves a multi-step drawer interface. This document outlines the validation checks and the criteria for progressing through these steps.</p>
+<p>The tenant creation process involves a multistep drawer interface. This document outlines the validation checks and the criteria for progressing through these steps.</p>
 <h2 id="step-1-enter-primary-info">Step 1: Enter Primary Info<a class="headerlink" href="#step-1-enter-primary-info" title="Permanent link">#</a></h2>
 <p><a class="glightbox" href="../../images/tenantCreationStep1.png" data-type="image" data-width="auto" data-height="auto" data-desc-position="bottom"><img alt="tenantCreationStep1" src="../../images/tenantCreationStep1.png" /></a></p>
 <p>The first step in creating a tenant is to provide a name for the tenant. Users must ensure the tenant name meets the specified criteria. The Next button remains disabled until the entered tenant name passes validation and a quota is selected.</p>
@@ -4372,8 +4372,8 @@ <h3 id="key-features_1">Key Features<a class="headerlink" href="#key-features_1"
 </ul>
 <h3 id="error-handling_2">Error Handling<a class="headerlink" href="#error-handling_2" title="Permanent link">#</a></h3>
 <ul>
-<li>The "Without Tenant Prefix" input validates namespace uniqueness and displays an error if the namespace already exists.</li>
-<li>Namespaces in the accordions are being verified before being addedif they already exists they are not added and shown with an error message on the input</li>
+<li>The "Without Tenant Prefix" input validates namespace uniqueness and displays an error if the namespace already exist.</li>
+<li>Namespaces in the accordions are being verified before being adde. If they already exist they are not added and shown with an error message on the input.</li>
 <li>No validation errors occur for annotations or labels as they are free-form inputs.</li>
 </ul>
 <h3 id="completion">Completion<a class="headerlink" href="#completion" title="Permanent link">#</a></h3>
@@ -4389,7 +4389,7 @@ <h2 id="update">Update<a class="headerlink" href="#update" title="Permanent link
 <p>User can click on the edit button in the table under the action items to open the drawer with all the pre-populated tenant configurations.</p>
 <p>The update process follows a similar flow to the create process. However, the key difference is that the <strong>tenant name</strong> in <strong>Step-1</strong> cannot be edited or updated. All other steps and configurations remain the same, allowing users to modify access control, namespaces, and metadata as needed.</p>
 <h2 id="delete">Delete<a class="headerlink" href="#delete" title="Permanent link">#</a></h2>
-<p>By clicking on the delete option in the tenants table the user will be able to perform delete operation and it may take a short while to delete the tenant.</p>
+<p>By clicking on the delete option in the tenants table the user will be able to perform delete operation, and it may take a short while to delete the tenant.</p>