clean build

docs/get-started/cost-billing/billing-process-for-harvard.md

@@ -32,11 +32,11 @@ Please follow these two steps to ensure proper billing setup:
 
     !!! abstract "What if you already have an existing Customer Code?"
 
-        Please note that if you already have an existing active NERC account, you
-        need to provide your HUIT Customer Code to NERC. If you think your department
-        may already have a HUIT account but you don’t know the corresponding Customer
-        Code then you can [contact HUIT Billing](https://billing.huit.harvard.edu/portal/allusers/contactus)
-        to get the required Customer Code.
+         Please note that if you already have an existing active NERC account, you
+         need to provide your HUIT Customer Code to NERC. If you think your department
+         may already have a HUIT account but you don’t know the corresponding Customer
+         Code then you can [contact HUIT Billing](https://billing.huit.harvard.edu/portal/allusers/contactus)
+         to get the required Customer Code.
 
 2.  During the Resource Allocation review and approval process, we will utilize the
     HUIT "Customer Code" provided by the PI in step #1 to align it with the approved

docs/openshift/applications/scaling-and-performance-guide.md

@@ -102,9 +102,9 @@ CPU and memory can be specified in a couple of ways:
 
     !!! note "Important Information"
 
-          If a Pod's total requests are not available on a single node, then the Pod
-          will remain in a *Pending* state (i.e. not running) until these resources
-          become available.
+        If a Pod's total requests are not available on a single node, then the Pod
+        will remain in a *Pending* state (i.e. not running) until these resources
+        become available.
 
 - The **limit** value specifies the max value you can consume. Limit is the value
   applications should be tuned to use. Pods will be memory, CPU throttled when
@@ -283,11 +283,11 @@ Click the **Observe** tab to:
 
     !!! note "Detailed Monitoring your project and application metrics"
 
-            On the left navigation panel of the **Developer** perspective, click
-            **Observe** to see the Dashboard, Metrics, Alerts, and Events for your project.
-            For more information about Monitoring project and application metrics
-            using the Developer perspective, please
-            [read this](https://docs.openshift.com/container-platform/4.10/applications/odc-monitoring-project-and-application-metrics-using-developer-perspective.html).
+        On the left navigation panel of the **Developer** perspective, click
+        **Observe** to see the Dashboard, Metrics, Alerts, and Events for your project.
+        For more information about Monitoring project and application metrics
+        using the Developer perspective, please
+        [read this](https://docs.openshift.com/container-platform/4.10/applications/odc-monitoring-project-and-application-metrics-using-developer-perspective.html).
 
 ## Scaling manually
 
@@ -402,8 +402,8 @@ maximum numbers to maintain the specified CPU utilization across all pods.
 
     !!! note "Configure via: Form or YAML View"
 
-          While creating or editing the horizontal pod autoscaler in the web console,
-          you can switch from **Form view** to **YAML view**.
+        While creating or editing the horizontal pod autoscaler in the web console,
+        you can switch from **Form view** to **YAML view**.
 
 - From the **Add HorizontalPodAutoscaler** form, define the name, minimum and maximum
   pod limits, the CPU and memory usage, and click **Save**.

docs/openshift/logging-in/web-console-overview.md

@@ -56,9 +56,9 @@ administrators and cluster administrators can view the Administrator perspective
 
 !!! note "Important Note"
 
-    The default web console perspective that is shown depends on the role of the
-    user. The **Administrator** perspective is displayed by default if the user
-    is recognized as an administrator.
+The default web console perspective that is shown depends on the role of the
+user. The **Administrator** perspective is displayed by default if the user is
+recognized as an administrator.
 
 ### About the Developer perspective in the web console
 
@@ -67,8 +67,8 @@ services, and databases.
 
 !!! info "Important Note"
 
-    The default view for the OpenShift Container Platform web console is the **Developer**
-    perspective.
+The default view for the OpenShift Container Platform web console is the **Developer**
+perspective.
 
 The web console provides a comprehensive set of tools for managing your projects
 and applications.
@@ -82,8 +82,8 @@ located on top navigation as shown below:
 
 !!! info "Important Note"
 
-    You can identify the currently selected project with **tick** mark and also
-    you can click on **star** icon to keep the project under your **Favorites** list.
+You can identify the currently selected project with **tick** mark and also
+you can click on **star** icon to keep the project under your **Favorites** list.
 
 ## Navigation Menu
 

docs/openstack/access-and-security/security-groups.md

@@ -79,8 +79,8 @@ Enter the following values:
 
     !!! note "Note"
 
-          To accept requests from a particular range of IP addresses, specify the
-          IP address block in the CIDR box.
+        To accept requests from a particular range of IP addresses, specify the IP
+        address block in the CIDR box.
 
 The new rule now appears in the list. This signifies that any instances using
 this newly added Security Group will now have SSH port 22 open for requests
@@ -141,10 +141,10 @@ Enter the following values:
 
 - CIDR: 0.0.0.0/0
 
-    !!! note "Note"
+!!! note "Note"
 
-          To accept requests from a particular range of IP addresses, specify the
-          IP address block in the CIDR box.
+    To accept requests from a particular range of IP addresses, specify the IP
+    address block in the CIDR box.
 
 The new rule now appears in the list. This signifies that any instances using
 this newly added Security Group will now have RDP port 3389 open for requests

docs/openstack/advanced-openstack-topics/setting-up-a-network/set-up-a-private-network.md

@@ -44,9 +44,9 @@ In the Create Network dialog box, specify the following values.
     networks, you should use IP addresses which fall within the ranges that are
     specifically reserved for private networks:
 
-          10.0.0.0/8
-          172.16.0.0/12
-          192.168.0.0/16
+                            10.0.0.0/8
+                            172.16.0.0/12
+                            192.168.0.0/16
 
     In the example below, we configure a network containing addresses 192.168.0.1
     to 192.168.0.255 using CIDR 192.168.0.0/24

docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md

@@ -126,10 +126,10 @@ To deactivate config: `wg-quick down /path/to/file_name.config`
 
 !!! note "Important Note"
 
-    You need to contact your project administrator to get your own WireGUard
-    configuration file (file with .conf extension). Download it and Keep it in
-    your local machine so in next steps we can use this configuration client
-    profile file.
+      You need to contact your project administrator to get your own WireGUard
+      configuration file (file with .conf extension). Download it and Keep it in
+      your local machine so in next steps we can use this configuration client
+      profile file.
 
 A WireGuard client or compatible software is needed to connect to the WireGuard
 VPN server. Please install[one of these clients](https://www.wireguard.com/install/)

docs/openstack/data-transfer/data-transfer-from-to-vm.md

@@ -434,20 +434,20 @@ using FTP, FTPS, SCP, SFTP, WebDAV, or S3 file transfer protocols.
 
 !!! info "Default User name based on OS"
 
-    - **all Ubuntu images**: ubuntu
+      - **all Ubuntu images**: ubuntu
 
-    - **all AlmaLinux images**: almalinux
+      - **all AlmaLinux images**: almalinux
 
-    - **all Rocky Linux images**: rocky
+      - **all Rocky Linux images**: rocky
 
-    - **all Fedora images**: fedora
+      - **all Fedora images**: fedora
 
-    - **all Debian images**: debian
+      - **all Debian images**: debian
 
-    - **all RHEL images**: cloud-user
+      - **all RHEL images**: cloud-user
 
-    If you still have VMs running with deleted **CentOS** images, you need to
-    use the following default username for your CentOS images: `centos`.
+      If you still have VMs running with deleted **CentOS** images, you need to
+      use the following default username for your CentOS images: `centos`.
 
 **"Password"**: "`<Leave blank as you using SSH key>`"
 
@@ -462,12 +462,12 @@ from the file picker.
 
 !!! tip "Helpful Tip"
 
-    You can save your above configured site with some preferred name by
-    clicking the "Save" button and then giving a proper name to your site.
-    This prevents needing to manually enter all of your configuration again the
-    next time you need to use WinSCP.
+      You can save your above configured site with some preferred name by
+      clicking the "Save" button and then giving a proper name to your site.
+      This prevents needing to manually enter all of your configuration again the
+      next time you need to use WinSCP.
 
-    ![Save Site WinSCP](images/winscp-save-site.png)
+      ![Save Site WinSCP](images/winscp-save-site.png)
 
 #### Using WinSCP
 
@@ -516,17 +516,17 @@ connections to servers, enterprise file sharing, and various cloud storage platf
 
 !!! info "Default User name based on OS"
 
-    - **all Ubuntu images**: ubuntu
+      - **all Ubuntu images**: ubuntu
 
-    - **all AlmaLinux images**: almalinux
+      - **all AlmaLinux images**: almalinux
 
-    - **all Rocky Linux images**: rocky
+      - **all Rocky Linux images**: rocky
 
-    - **all Fedora images**: fedora
+      - **all Fedora images**: fedora
 
-    - **all Debian images**: debian
+      - **all Debian images**: debian
 
-    - **all RHEL images**: cloud-user
+      - **all RHEL images**: cloud-user
 
 **"Password"**: "`<Leave blank as you using SSH key>`"
 
@@ -585,20 +585,20 @@ computer (shared drives, Dropbox, etc.)
 
 !!! info "Default User name based on OS"
 
-    - **all Ubuntu images**: ubuntu
+      - **all Ubuntu images**: ubuntu
 
-    - **all AlmaLinux images**: almalinux
+      - **all AlmaLinux images**: almalinux
 
-    - **all Rocky Linux images**: rocky
+      - **all Rocky Linux images**: rocky
 
-    - **all Fedora images**: fedora
+      - **all Fedora images**: fedora
 
-    - **all Debian images**: debian
+      - **all Debian images**: debian
 
-    - **all RHEL images**: cloud-user
+      - **all RHEL images**: cloud-user
 
-    If you still have VMs running with deleted **CentOS** images, you need to
-    use the following default username for your CentOS images: `centos`.
+      If you still have VMs running with deleted **CentOS** images, you need to
+      use the following default username for your CentOS images: `centos`.
 
 **"Key file"**: "Browse and choose the appropriate SSH Private Key from you
 local machine that has corresponding Public Key attached to your VM"

docs/openstack/openstack-cli/openstack-CLI.md

@@ -37,10 +37,10 @@ You can download the environment file with the credentials from the [OpenStack d
 
 !!! note "Important Note"
 
-    Please note that an application credential is only valid for a single
-    project, and to access multiple projects you need to create an application
-    credential for each. You can switch projects by clicking on the project name
-    at the top right corner and choosing from the dropdown under "Project".
+      Please note that an application credential is only valid for a single
+      project, and to access multiple projects you need to create an application
+      credential for each. You can switch projects by clicking on the project name
+      at the top right corner and choosing from the dropdown under "Project".
 
 After clicking "Create Application Credential" button, the **ID** and
 **Secret** will be displayed and you will be prompted to `Download openrc file`

docs/openstack/persistent-storage/mount-the-object-storage.md

@@ -59,7 +59,7 @@ parts are `EC2_ACCESS_KEY` and `EC2_SECRET_KEY`, keep them noted.
 - Allow Other User option by editing fuse config by editing `/etc/fuse.conf` file
   and uncomment "user_allow_other" option.
 
-                  sudo nano /etc/fuse.conf
+          sudo nano /etc/fuse.conf
 
 The output going to look like this:
 
@@ -977,9 +977,9 @@ Also, check that binding to `localhost` is working fine by running the following
 
 !!! warning "Important Note"
 
-    The `netstat` command may not be available on your system by default. If
-    this is the case, you can install it (along with a number of other handy
-    networking tools) with the following command: `sudo apt install net-tools`.
+      The `netstat` command may not be available on your system by default. If
+      this is the case, you can install it (along with a number of other handy
+      networking tools) with the following command: `sudo apt install net-tools`.
 
 ##### Configuring a Redis Password
 

docs/openstack/persistent-storage/object-storage.md

@@ -256,13 +256,13 @@ This is a python client for the Swift API. There's a [Python API](https://github
 - This example uses a `Python3` virtual environment, but you are free to choose
   any other method to create a local virtual environment like `Conda`.
 
-                  python3 -m venv venv
+          python3 -m venv venv
 
 !!! note "Choosing Correct Python Interpreter"
 
-    Make sure you are able to use `python` or `python3` or **`py -3`** (For
-    Windows Only) to create a directory named `venv` (or whatever name you
-    specified) in your current working directory.
+      Make sure you are able to use `python` or `python3` or **`py -3`** (For
+      Windows Only) to create a directory named `venv` (or whatever name you
+      specified) in your current working directory.
 
 - Activate the virtual environment by running:
 
@@ -526,8 +526,8 @@ directory `~/.aws/config` with the ec2 profile and credentials as shown below:
 
 !!! note "Information"
 
-    We need to have a profile that you use must have permissions to allow
-    the AWS operations can be performed.
+      We need to have a profile that you use must have permissions to allow
+      the AWS operations can be performed.
 
 #### Listing buckets using **aws-cli**
 
@@ -1062,9 +1062,9 @@ respectively.
 
 !!! note "Helpful Tips"
 
-    You can save your above configured session with some preferred name by
-    clicking the "Save" button and then giving a proper name to your session.
-    So that next time you don't need to again manually enter all your configuration.
+      You can save your above configured session with some preferred name by
+      clicking the "Save" button and then giving a proper name to your session.
+      So that next time you don't need to again manually enter all your configuration.
 
 #### Using WinSCP
 

docs/openstack/persistent-storage/transfer-a-volume.md

@@ -104,9 +104,9 @@ openstack volume transfer request create my-volume
 
 !!! tip "Pro Tip"
 
-    If your volume name includes spaces, you need to enclose them in quotes,
-    i.e. `"<VOLUME_NAME_OR_ID>"`.
-    For example: `openstack volume transfer request create "My Volume"`
+      If your volume name includes spaces, you need to enclose them in quotes,
+      i.e. `"<VOLUME_NAME_OR_ID>"`.
+      For example: `openstack volume transfer request create "My Volume"`
 
 - The volume can be checked as in the transfer status using
   `openstack volume transfer request list` as follows and the volume is in status

docs/other-tools/CI-CD/github-actions/setup-github-actions-pipeline.md

@@ -84,14 +84,14 @@ workflow.
 
         !!! info "Very Important Information"
 
-              Workflow execution on OpenShift pipelines follows these steps:
-
-              1. Checkout your repository
-              2. Perform a container image build
-              3. Push the built image to the GitHub Container Registry (GHCR) or
-              your preferred Registry
-              4. Log in to your NERC OpenShift cluster's project space
-              5. Create an OpenShift app from the image and expose it to the internet
+            Workflow execution on OpenShift pipelines follows these steps:
+
+            1. Checkout your repository
+            2. Perform a container image build
+            3. Push the built image to the GitHub Container Registry (GHCR) or
+            your preferred Registry
+            4. Log in to your NERC OpenShift cluster's project space
+            5. Create an OpenShift app from the image and expose it to the internet
 
 8.  Edit the top-level 'env' section as marked with '🖊️' if the defaults are not
     suitable for your project.