Updates attributes (#599)

Co-authored-by: Steven Smith <stevsmit@stevsmit.remote.csb>

Author: stevsmit

modules/backing-up-red-hat-quay-standalone.adoc

@@ -1,38 +1,38 @@
 :_content-type: PROCEDURE
 [[backing-up-red-hat-quay-standalone]]
-= Backing up {productname} on standalone deployments 
+= Backing up {productname} on standalone deployments
 
-This procedure describes how to create a backup of {productname} on standalone deployments. 
+This procedure describes how to create a backup of {productname} on standalone deployments.
 
 .Prerequisites
 
-.Procedure 
+.Procedure
 
-. Create a temporary backup directory, for example, `quay-backup`: 
+. Create a temporary backup directory, for example, `quay-backup`:
 +
 [source,terminal]
 ----
 $ mkdir /tmp/quay-backup
 ----
 
-. The following example command denotes the local directory that the {productname} was started in, for example, `/opt/quay-install`: 
+. The following example command denotes the local directory that the {productname} was started in, for example, `/opt/quay-install`:
 +
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ podman run --name quay-app \
    -v /opt/quay-install/config:/conf/stack:Z \
    -v /opt/quay-install/storage:/datastorage:Z \
    {productrepo}/{quayimage}:{productminv}
 ----
 +
-Change into the directory that bind-mounts to `/conf/stack` inside of the container, for example, `/opt/quay-install`, by running the following command: 
+Change into the directory that bind-mounts to `/conf/stack` inside of the container, for example, `/opt/quay-install`, by running the following command:
 +
 [source,terminal]
 ----
 $ cd /opt/quay-install
 ----
 
-. Compress the contents of your {productname} deployment into an archive in the `quay-backup` directory by entering the following command: 
+. Compress the contents of your {productname} deployment into an archive in the `quay-backup` directory by entering the following command:
 +
 [source,terminal]
 ----
@@ -51,9 +51,9 @@ ssl.cert
 ssl.key
 ----
 
-. Back up the Quay container service by entering the following command: 
+. Back up the Quay container service by entering the following command:
 +
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ podman inspect quay-app | jq -r '.[0].Config.CreateCommand | .[]' | paste -s -d ' ' -
 
@@ -63,11 +63,11 @@ $ podman inspect quay-app | jq -r '.[0].Config.CreateCommand | .[]' | paste -s -
   {productrepo}/{quayimage}:{productminv}
 ----
 
-. Redirect the contents of your `conf/stack/config.yaml` file to your temporary `quay-config.yaml` file by entering the following command: 
+. Redirect the contents of your `conf/stack/config.yaml` file to your temporary `quay-config.yaml` file by entering the following command:
 +
 [source,terminal]
 ----
-$ podman exec -it quay cat /conf/stack/config.yaml > /tmp/quay-backup/quay-config.yaml 
+$ podman exec -it quay cat /conf/stack/config.yaml > /tmp/quay-backup/quay-config.yaml
 ----
 
 . Obtain the `DB_URI` located in your temporary `quay-config.yaml` by entering the following command:
@@ -90,15 +90,15 @@ $ postgresql://<username>:test123@172.24.10.50/quay
 $ pg_dump -h 172.24.10.50  -p 5432 -d quay  -U  <username>   -W -O > /tmp/quay-backup/quay-backup.sql
 ----
 
-. Print the contents of your `DISTRIBUTED_STORAGE_CONFIG` by entering the following command: 
+. Print the contents of your `DISTRIBUTED_STORAGE_CONFIG` by entering the following command:
 +
 [source,yaml]
 ----
 DISTRIBUTED_STORAGE_CONFIG:
    default:
     - S3Storage
     - s3_bucket: <bucket_name>
-      storage_path: /registry 
+      storage_path: /registry
       s3_access_key: <s3_access_key>
       s3_secret_key: <s3_secret_key>
       host: <host_name>
@@ -108,7 +108,7 @@ DISTRIBUTED_STORAGE_CONFIG:
 +
 [source,terminal]
 ----
-$ export AWS_ACCESS_KEY_ID=<access_key> 
+$ export AWS_ACCESS_KEY_ID=<access_key>
 ----
 
 . Export the `AWS_SECRET_ACCESS_KEY` by using the `secret_key` obtained in Step 7:
@@ -133,5 +133,5 @@ download: s3://<user_name>/registry/sha256/e9/e9c5463f15f0fd62df3898b36ace8d1538
 ----
 [NOTE]
 ====
-It is recommended that you delete the `quay-config.yaml` file after syncing the `quay` bucket because it contains sensitive information. The `quay-config.yaml` file will not be lost because it is backed up in the `quay-backup.tar.gz` file. 
+It is recommended that you delete the `quay-config.yaml` file after syncing the `quay` bucket because it contains sensitive information. The `quay-config.yaml` file will not be lost because it is backed up in the `quay-backup.tar.gz` file.
 ====

modules/clair-standalone-quay-config.adoc

@@ -4,12 +4,12 @@
 . Stop the `Quay` container if it is running, and restart it in configuration mode, loading the existing configuration as a volume:
 +
 [subs="verbatim,attributes"]
-....
-$ sudo podman run --rm -it --name quay_config \ 
+----
+$ sudo podman run --rm -it --name quay_config \
   -p 80:8080 -p 443:8443 \
   -v $QUAY/config:/conf/stack:Z \
   {productrepo}/{quayimage}:{productminv} config secret
-....
+----
 
 . Log in to the configuration tool and enable scanning in the Security Scanner section of the UI. Set the HTTP endpoint for Clair using a port that is not already in use on the `quay-server` system, for example `8081`. Create a Clair pre-shared key (PSK) using the `Generate PSK` button, for example:
 +

modules/clair-standalone-running.adoc

@@ -9,17 +9,17 @@ $ sudo podman run -d --rm --name clairv4 \
   -p 8081:8081 -p 8089:8089 \
   -e CLAIR_CONF=/clair/config.yaml -e CLAIR_MODE=combo \
   -v /etc/clairv4/config:/clair:Z \
-  {productrepo}/{clairimage}:{productminv} 
+  {productrepo}/{clairimage}:{productminv}
 ....
 
 
 . Next, restart the `Quay` container using the updated configuration file containing the scanner settings:
 +
 [subs="verbatim,attributes"]
-....
+----
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443  \
    --name=quay \
    -v $QUAY/config:/conf/stack:Z \
    -v $QUAY/storage:/datastorage:Z \
    {productrepo}/{quayimage}:{productminv}
-....
+----

modules/config-api-default.adoc

@@ -1,13 +1,13 @@
-= Retrieving the default configuration 
+= Retrieving the default configuration
 
 If you are running the configuration tool for the first time, and do not have an existing configuration, you can retrieve the default configuration. Start the container in config mode:
 
 [subs="verbatim,attributes"]
-....
-$ sudo podman run --rm -it --name quay_config \ 
+----
+$ sudo podman run --rm -it --name quay_config \
   -p 8080:8080 \
   {productrepo}/{quayimage}:{productminv} config secret
-....
+----
 
 Use the `config` endpoint of the configuration API to get the default:
 

modules/config-api-retrieve.adoc

@@ -3,12 +3,12 @@
 If you have already configured and deployed the Quay registry, stop the container and restart it in configuration mode, loading the existing configuration as a volume:
 
 [subs="verbatim,attributes"]
-....
-$ sudo podman run --rm -it --name quay_config \ 
+----
+$ sudo podman run --rm -it --name quay_config \
   -p 8080:8080 \
   -v $QUAY/config:/conf/stack:Z \
   {productrepo}/{quayimage}:{productminv} config secret
-....
+----
 
 Use the `config` endpoint of the API to get the current configuration:
 

modules/config-file-location.adoc

@@ -2,9 +2,9 @@
 [id="config-file-location"]
 = Location of configuration file in a standalone deployment
 
-For standalone deployments of {productname}, the `config.yaml` file must be specified when starting the {productname} registry. This file is located in the configuration volume. For example, the configuration file is located at `$QUAY/config/config.yaml` when deploying {productname} by the following command: 
+For standalone deployments of {productname}, the `config.yaml` file must be specified when starting the {productname} registry. This file is located in the configuration volume. For example, the configuration file is located at `$QUAY/config/config.yaml` when deploying {productname} by the following command:
 
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
    --name=quay \

modules/config-file-minimal.adoc

@@ -2,7 +2,7 @@
 [id="config-file-minimal"]
 = Minimal configuration
 
-The following configuration options are required for a standalone deployment of {productname}: 
+The following configuration options are required for a standalone deployment of {productname}:
 
 * Server hostname
 * HTTP or HTTPS
@@ -16,7 +16,7 @@ The following configuration options are required for a standalone deployment of
 [id="sample-config-file-minimal"]
 == Sample minimal configuration file
 
-The following example shows a sample minimal configuration file that uses local storage for images: 
+The following example shows a sample minimal configuration file that uses local storage for images:
 
 [source,yaml]
 ----
@@ -60,11 +60,11 @@ The `SETUP_COMPLETE` field indicates that the configuration has been validated.
 [id="config-local-storage"]
 == Local storage
 
-Using local storage for images is only recommended when deploying a registry for proof of concept purposes. 
+Using local storage for images is only recommended when deploying a registry for proof of concept purposes.
 
-When configuring local storage, storage is specified on the command line when starting the registry. The following command maps a local directory, `$QUAY/storage` to the `datastorage` path in the container: 
+When configuring local storage, storage is specified on the command line when starting the registry. The following command maps a local directory, `$QUAY/storage` to the `datastorage` path in the container:
 
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
    --name=quay \
@@ -76,7 +76,7 @@ $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
 [id="config-cloud-storage"]
 == Cloud storage
 
-Storage configuration is detailed in the xref:config-fields-storage[Image storage] section. For some users, it might be useful to compare the difference between Google Cloud Platform and local storage configurations. For example, the following YAML presents a Google Cloud Platform storage configuration: 
+Storage configuration is detailed in the xref:config-fields-storage[Image storage] section. For some users, it might be useful to compare the difference between Google Cloud Platform and local storage configurations. For example, the following YAML presents a Google Cloud Platform storage configuration:
 
 .$QUAY/config/config.yaml
 [source,yaml]
@@ -95,7 +95,7 @@ DISTRIBUTED_STORAGE_PREFERENCE:
 
 When starting the registry using cloud storage, no configuration is required on the command line. For example:
 
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
    --name=quay \

modules/georepl-deploy-standalone.adoc

@@ -11,13 +11,13 @@ For example, for a machine running in Europe with the config
 directory on the host available from `$QUAY/config`:
 +
 [subs="verbatim,attributes"]
-....
+----
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443  \
    --name=quay \
    -v $QUAY/config:/conf/stack:Z \
    -e QUAY_DISTRIBUTED_STORAGE_PREFERENCE=europestorage \
    {productrepo}/{quayimage}:{productminv}
-....
+----
 +
 [NOTE]
 ====

modules/mirroring-worker.adoc

@@ -1,25 +1,25 @@
 [id="mirroring-worker"]
 = Mirroring worker
 
-Use the following procedure to start the repository mirroring worker. 
+Use the following procedure to start the repository mirroring worker.
 
-.Procedure 
+.Procedure
 
-* If you have not configured TLS communications using a `/root/ca.crt` certificate, enter the following command to start a `Quay` pod with the `repomirror` option: 
+* If you have not configured TLS communications using a `/root/ca.crt` certificate, enter the following command to start a `Quay` pod with the `repomirror` option:
 +
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ sudo podman run -d --name mirroring-worker \
   -v $QUAY/config:/conf/stack:Z \
   {productrepo}/{quayimage}:{productminv} repomirror
 ----
 
-* If you have configured TLS communications using a `/root/ca.crt` certificate, enter the following command to start the repository mirroring worker: 
+* If you have configured TLS communications using a `/root/ca.crt` certificate, enter the following command to start the repository mirroring worker:
 +
-[source,terminal]
+[subs="verbatim,attributes"]
 ----
 $ sudo podman run -d --name mirroring-worker \
   -v $QUAY/config:/conf/stack:Z \
   -v /root/ca.crt:/etc/pki/ca-trust/source/anchors/ca.crt:Z \
-  {productrepo}/{quayimage}:{productminv} repomirror 
+  {productrepo}/{quayimage}:{productminv} repomirror
 ----

modules/proc_deploy_quay_common_superuser.adoc

@@ -11,20 +11,20 @@ A `superuser` is a Quay user account that has extended privileges, including the
 
 == Adding a superuser to Quay using the UI
 
-This section covers how to add a superuser using the Quay UI. To add a superuser using the command line interface, see the following section. 
+This section covers how to add a superuser using the Quay UI. To add a superuser using the command line interface, see the following section.
 
 . Start the `Quay` container in configuration mode, loading the existing configuration as a volume:
 +
 [subs="verbatim,attributes"]
 ....
-$ sudo podman run --rm -it --name quay_config \ 
+$ sudo podman run --rm -it --name quay_config \
   -p 8080:8080 \
   -p 443:8443 \
   -v $QUAY/config:/conf/stack:Z \
   {productrepo}/{quayimage}:{productminv} config secret
 ....
 
-. Under the `Access Settings` section of the UI, enter the name of the user (in this instance, `quayadmin`) in the `Super Users` field and click `Add`. 
+. Under the `Access Settings` section of the UI, enter the name of the user (in this instance, `quayadmin`) in the `Super Users` field and click `Add`.
 
 . Validate and download the `configuration` file and then terminate the `Quay` container that is running in config mode. Extract the `config.yaml` file to the configuration directory and restart the `Quay` container in registry mode:
 +
@@ -37,13 +37,13 @@ $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
 -v $QUAY/storage:/datastorage:Z \
 {productrepo}/{quayimage}:{productminv}
 ```
- 
+
 
 == Editing the config.yaml file to add a superuser
 
 You can also add a superuser by editing the `config.yaml` file directly. The list of superuser accounts is stored as an array in the field `SUPER_USERS`.
 
-* Stop the container registry if it is running, and add the `SUPER_USERS` array to the `config.yaml` file: 
+* Stop the container registry if it is running, and add the `SUPER_USERS` array to the `config.yaml` file:
 +
 [source,yaml]
 ----
@@ -56,33 +56,33 @@ SUPER_USERS:
 
 == Accessing the superuser admin panel
 
-. Restart the Quay registry: 
+. Restart the Quay registry:
 +
 [subs="verbatim,attributes"]
-```
+----
 $ sudo podman rm -f quay
 $ sudo podman run -d --rm -p 80:8080 -p 443:8443 \
 --name=quay \
 -v $QUAY/config:/conf/stack:Z \
 -v $QUAY/storage:/datastorage:Z \
 {productrepo}/{quayimage}:{productminv}
-```
+----
 . Access the Super User Admin Panel by clicking on the current user's name or avatar in the top right-hand corner of the UI. If the user has been added as a superuser, an extra item is presented in the drop-down list called Super User Admin Panel.
 +
 image:super-user-admin-panel.png[Super User Admin Panel]
 
 === Creating a globally visible user message
 
-Using the Superuser Admin Panel, you can create `Normal`, `Warning`, or `Error` messages for your organization. 
+Using the Superuser Admin Panel, you can create `Normal`, `Warning`, or `Error` messages for your organization.
 
-. Click your user name in the top right-hand corner of the UI. Select `Super User Admin Panel`. 
+. Click your user name in the top right-hand corner of the UI. Select `Super User Admin Panel`.
 
-. On the {productname} Management page, click `Globally visible user messages` on the left hand pane. 
+. On the {productname} Management page, click `Globally visible user messages` on the left hand pane.
 
-. Click `Create Message` to show a drop-down menu containing `Normal`, `Warning`, and `Error` message types: 
+. Click `Create Message` to show a drop-down menu containing `Normal`, `Warning`, and `Error` message types:
 +
 image:create-new-message.png[Creating a new messsage]
 
-. Enter a message by selecting `Click to set message`, then click `Create Message`. 
+. Enter a message by selecting `Click to set message`, then click `Create Message`.
 
-Messages can be deleted by clicking `Options` and then `Delete Message`.  
+Messages can be deleted by clicking `Options` and then `Delete Message`.