Small edits to troubleshooting guide (#734)

stevsmit · Steven Smith · web-flow · commit 954174ca3764 · 2023-07-19T16:17:46.000-04:00
Co-authored-by: Steven Smith &lt;stevsmit@stevsmit.remote.csb&gt;
diff --git a/.vale.ini b/.vale.ini
@@ -0,0 +1,8 @@
+StylesPath = styles
+
+MinAlertLevel = suggestion
+
+Packages = RedHat
+
+[*]
+BasedOnStyles = RedHat
diff --git a/.vale/styles/Vocab/OpenShiftDocs/accept.txt b/.vale/styles/Vocab/OpenShiftDocs/accept.txt
@@ -0,0 +1,11 @@
+# Regex terms added to accept.txt are ignored by the Vale linter and override RedHat Vale rules.
+# Add terms that have a corresponding incorrectly capitalized form to reject.txt.
+
+[Pp]assthrough
+Assisted Installer
+Control Plane Machine Set Operator
+custom resource
+custom resources
+MetalLB
+Operator
+Operators
diff --git a/.vale/styles/Vocab/OpenShiftDocs/reject.txt b/.vale/styles/Vocab/OpenShiftDocs/reject.txt
@@ -0,0 +1,15 @@
+# Regex terms added to reject.txt are highlighted as errors by the Vale linter and override RedHat Vale rules.
+# Add terms that have a corresponding correctly capitalized form to accept.txt.
+
+[Dd]eployment [Cc]onfigs?
+[Dd]eployment [Cc]onfigurations?
+[Oo]peratorize
+[Ss]ingle [Nn]ode OpenShift
+[Tt]hree [Nn]ode OpenShift
+AI
+configuration maps?
+MachineSets
+machinesets?
+minions?
+operators?
+SNO
diff --git a/modules/authentication-troubleshooting.adoc b/modules/authentication-troubleshooting.adoc
@@ -14,4 +14,4 @@ The following authentication methods are supported by {productname}:
 
 * *Token-based authentication*. Users can obtain unique tokens that grant access to specific resources within {productname}. Tokens can be obtained through various means, such as OAuth or by generating API tokens within the {productname} user interface. Token-based authentication is often used for automated or programmatic access to the registry.
 
-* *External identity provider*. {productname} can integrate with external identity providers, such as LDAP or AzureAD, for authentication purposes. This integration allows organizations to leverage their existing identity management infrastructure, enabling centralized user authentication and reducing the need for separate user databases.
+* *External identity provider*. {productname} can integrate with external identity providers, such as LDAP or AzureAD, for authentication purposes. This integration allows organizations to use their existing identity management infrastructure, enabling centralized user authentication and reducing the need for separate user databases.
diff --git a/modules/build-logs-not-loading.adoc b/modules/build-logs-not-loading.adoc
@@ -2,4 +2,4 @@
 [id="build-logs-not-loading"]
 = Build logs are not loading
 
-In some cases, attempting to load logs for a repository build results in only a throbber, and no logs are displayed. This typically occurs when you are using a browser equipped with one of the following extensions: AdBlock, uBlock, or Privacy Badger. These browser extensions can cause the loading of build logs to be cancelled. To resolve this issue, disable the browser extension and reload the page.
+In some cases, attempting to load logs for a repository build results in only a throbber icon, and no logs are displayed. This typically occurs when you are using a browser equipped with one of the following extensions: AdBlock, uBlock, or Privacy Badger. These browser extensions can cause the loading of build logs to be cancelled. To resolve this issue, disable the browser extension and reload the page.
diff --git a/modules/build-trigger-error.adoc b/modules/build-trigger-error.adoc
@@ -1,5 +1,5 @@
 :_content-type: CONCEPT
 [id="build-trigger-error"]
-= Unable to add a Build Trigger
+= Unable to add a build trigger
 
-In some cases, attempting to add a Build Trigger results in the following error message: `You are not admin on the SCM repository`. In order for {productname} to add the webhook callback necessary for Build Triggers, the user granting {productname} access to the SCM repository must have administrative access on that repository. 
+In some cases, attempting to add a build trigger results in the following error message: `You are not admin on the SCM repository`. In order for {productname} to add the webhook callback necessary for Build Triggers, the user granting {productname} access to the SCM repository must have administrative access on that repository. 
diff --git a/modules/cannot-access-private-repo.adoc b/modules/cannot-access-private-repo.adoc
@@ -2,7 +2,7 @@
 [id="cannot-access-private-repo"]
 = Unable to access private repositories using Amazon EC2 Container Service
 
-In some cases, authentication fails while attempting to use Amazon Elastic Container Service (EC2). This error occurs when the authentication configuration in the `ecs.config` file is missing. 
+In some cases, authentication fails while attempting to use Amazon Elastic Container Service (ECS). This error occurs when the authentication configuration in the `ecs.config` file is missing. 
 
 In order for ECS to pull down Docker images, the following information must be included in the ECS configuration file that is located in the `/etc/ecs/ecs.conf` file:
 
diff --git a/modules/cannot-locate-dockerfile.adoc b/modules/cannot-locate-dockerfile.adoc
@@ -6,4 +6,4 @@ When building an image, the following error is returned: `A build step failed: A
 
 * *The `.dockerignore` file contains the Dockerfile.* Unlike Docker Hub, the Dockerfile is part of the Build Context on {productname}. The Dockerfile must not appear in the `.dockerignore` file. Remove the Dockerfile from the `.dockerignore` file to resolve the issue. 
 
-* *The Build Trigger is incorrect.* Verify the Dockerfile location and the branch/tag value specified in the Build Trigger.
+* *The build trigger is incorrect.* Verify the Dockerfile location and the branch or tag value specified in the build trigger.
diff --git a/modules/cannot-reach-registry-endpoint.adoc b/modules/cannot-reach-registry-endpoint.adoc
@@ -2,4 +2,4 @@
 [id="cannot-reach-registry-endpoint"]
 = Unable to reach registry endpoint
 
-In some cases, attempting to pull a Docker image returns the following error: `Could not reach any registry endpoint`. This usually occurs because you are attempting to pull a non-existent tag. If you do not specify a tag, newer version of Docker attempt to pull the "latest" tag, regardless of whether it actually exists. 
+In some cases, trying to pull a Docker image returns the following error: `Could not reach any registry endpoint`. This usually occurs because you are attempting to pull a non-existent tag. If you do not specify a tag, newer version of Docker attempt to pull the "latest" tag, regardless of whether it actually exists. 
diff --git a/modules/clair-distroless-container-images.adoc b/modules/clair-distroless-container-images.adoc
@@ -1,5 +1,5 @@
 :_content-type: CONCEPT
 [id="clair-distroless-container-images"]
-= Does Clair supporting scanning of distoless container images? 
+= Does Clair supporting scanning of disto-less container images? 
 
-Support for scanning distroless containers was added in Clair 4.6.1. This feature is not present in earlier versions. For Clair on the {productname} Operator, this feature was released with {productname} 3.8.7.
+Support for scanning distro-less containers was added in Clair 4.6.1. This feature is not present in earlier versions. For Clair on the {productname} Operator, this feature was released with {productname} 3.8.7.
diff --git a/modules/clair-troubleshooting-issues.adoc b/modules/clair-troubleshooting-issues.adoc
@@ -112,7 +112,7 @@ $ podman logs clair-container
 [id="updating-cve-database"]
 == Updating the CVE database 
 
-Updating the CVE database can be a memory and CPU intensive task, especially if there are several CVEs that must be parsed. If the resources are exhausted during this process, the system kernel can terminate the offending process. This should be visible in Docker logs, Podman logs, or in the system journal. For example:
+Updating the CVE database can be a memory and CPU intensive task, especially if there are several CVEs that must be parsed. If the resources are exhausted during this process, the system kernel can stop the offending process. This should be visible in Docker logs, Podman logs, or in the system journal. For example:
 
 [source,terminal]
 ----
diff --git a/modules/connecting-s3-timeout.adoc b/modules/connecting-s3-timeout.adoc
@@ -6,7 +6,7 @@ In some cases, {productname} attempts to connect to the s3 bucket that is descri
 
 This error occurs because the URL format of a bucket is one of two options. For example:
 
-* `http://s3.amazonaws.com/[bucket_name]/`
+* `\http://s3.amazonaws.com/[bucket_name]/`
 * `http://[bucket_name].s3.amazonaws.com/`
 
 To resolve this issue, you must add the `s3_region` configuration parameter to your `config.yaml` file. This field is not currently embedded in the {productname} config editor, so it must be manually added. If this field is not present in your `config.yaml` file, the Authorization header explicitly mentions a different region and not the region set in the `hostname` field of your `config.yaml` file. 
diff --git a/modules/database-troubleshooting-issues.adoc b/modules/database-troubleshooting-issues.adoc
@@ -316,7 +316,7 @@ $ podman stats <container_name>
 postgres=# \l+
 ----
 
-. Enter the following command to connect with the PostgreSQL database:
+. Enter the following command to connect to the PostgreSQL database:
 +
 [source,terminal]
 ----
diff --git a/modules/deleting-user-cli.adoc b/modules/deleting-user-cli.adoc
@@ -1,6 +1,6 @@
 :_content-type: CONCEPT
 [id="deleting-user-cli"]
-= Deleting a user from {productname} from the command line
+= Deleting a {productname} user from the command line
 
 When accessing the *Users* tab in the *Superuser Admin* panel of the {productname} UI, you might encounter a situation where no users are listed. Instead, a message appears, indicating that {productname} is configured to use external authentication, and users can only be created in that system.
 
diff --git a/modules/docker-failing-pulls.adoc b/modules/docker-failing-pulls.adoc
@@ -4,7 +4,7 @@
 
 In some cases, using `docker pull` might return the following error: `39cb5a2eab5d: Error pulling image (myimage) from quay.io/my/repository. . .  Could not find repository on any of the indexed registries.` There are two reasons for receiving this error. 
 
-* *Linux kernel bug on Ubuntu Precise Pangolin (12.04 LTS) (64-bit).* Precise has a Linux kernel bug that must be updated in order to use Docker. Use the following commands to update and reboot Precise. 
+* *Linux kernel bug on Ubuntu Precise Pangolin (12.04 LTS) (64-bit).* Precise has a Linux kernel bug that must be updated to use Docker. Use the following commands to update and reboot Precise. 
 +
 [source,terminal]
 ----
@@ -21,7 +21,7 @@ $ sudo apt-get install linux-image-generic-lts-raring linux-headers-generic-lts-
 $ sudo reboot
 ----
 
-* *Missing AUFS on Raring 13.04 and Saucy 13.10 (64-bit).* Not all installations of Ubuntu 13.04/13.10 ship with AUFS enabled. Enter the following commands to install additional Linux kernel modules:
+* *Missing AUFS on Raring 13.04 and Saucy 13.10 (64-bit).* Not all installations of Ubuntu 13.04 or 13.10 include AUFS enabled. Enter the following commands to install additional Linux kernel modules:
 +
 [source,terminal]
 ----
diff --git a/modules/error-403-troubleshooting.adoc b/modules/error-403-troubleshooting.adoc
@@ -27,12 +27,12 @@ For more information, see link:https://github.com/moby/moby/issues/4267[Dockercf
 
 Docker stores the credentials that it uses for pushing and pulling in a file that is usually placed in the `$HOME/.docker/config.json` folder. If you are executing Docker in another environment, such as a scripted `docker build`, a virtual machine, `makefile`, `virtualenv`, and so on, Docker cannot find the `config.json` file and fails. 
 
-As a workaround, make sure that the `config.json` file is accessible to the environment which is performing the push or pull commands. 
+As a workaround, verify that the `config.json` file is accessible to the environment which is performing the push or pull commands. 
 
 [id="repository-permissions"]
 == Insufficient repository permissions
 
-Ensure that your user, robot account, or token has sufficient permissions on the repository. Permissions on a repository can be edited from the *Settings* -> *Repository settings* page. 
+Ensure that your user, robot account, or token has the necessary permissions on the repository. Permissions on a repository can be edited from the *Settings* -> *Repository settings* page. 
 
 [NOTE]
 ====
diff --git a/modules/error-429-troubleshooting.adoc b/modules/error-429-troubleshooting.adoc
@@ -6,6 +6,6 @@ HTTP status code `429` indicates that the user has sent too many requests in a g
 
 * Reduce the frequency or pace at which you are sending requests to your {productname} registry. This helps ensure that you stay within the allowed limits and avoid triggering a `429` response. 
 
-* Implement a backoff strategy to wait and retry the request after a certain period of time. Backoff strategies involve increasing the waiting time between subsequent requests. This gives the server enough time to process previous requests, which avoids overwhelming the server. 
+* Implement a back-off strategy to wait and retry the request after a certain period of time. Back-off strategies involve increasing the waiting time between subsequent requests. This gives the server enough time to process previous requests, which avoids overwhelming the server. 
 
-* Utilize caching mechanisms to store and reuse frequently accessed data from the {productname} registry. This can help reduce the need for repeated requests and improve overall performance. 
+* Use caching mechanisms to store and reuse frequently accessed data from the {productname} registry. This can help reduce the need for repeated requests and improve overall performance. 
diff --git a/modules/error-500-troubleshooting.adoc b/modules/error-500-troubleshooting.adoc
@@ -12,7 +12,7 @@ To resolve this issue, you can increase the database connection count by using t
 
 . Navigate to your `/var/lib/pgsql/data/postgresql.conf` file. 
 
-. Increase the database connection count by updating the the `max_connections` variable. It is recommended to set the number of connections on the database to at least `1000` for a development cluster, and `2000` for a production cluster. In some cases you might need more. For example:
+. Increase the database connection count by updating the `max_connections` variable. It is recommended to set the number of connections on the database to at least `1000` for a development cluster, and `2000` for a production cluster. In some cases you might need more. For example:
 +
 [source,yaml]
 ----
diff --git a/modules/error-502-troubleshooting.adoc b/modules/error-502-troubleshooting.adoc
@@ -43,14 +43,14 @@ If you run {productname} in debug mode and the error `peewee.DataError: integer
 
 .Procedure 
 
-* In most cases, a {productname} administrator can resolve this error by setting the `FEATURE_CHANGE_TAG_EXPIRATION` configuration field to `false` in their `config.yaml` file. 
+. In most cases, a {productname} administrator can resolve this error by setting the `FEATURE_CHANGE_TAG_EXPIRATION` configuration field to `false` in their `config.yaml` file. 
 +
 [NOTE]
 ====
 This change affects all users of your organization and disables them from setting tag expirations themselves. 
 ====
 
-* Alternatively, you can request the user or owner of the repository in question to either remove, or change, the tag expiration manually. If they do not respond, you can execute the following steps:
+. Alternatively, you can request the user or owner of the repository in question to either remove, or change, the tag expiration manually. If they do not respond, you can execute the following steps:
 +
 ** Obtain information from the user table:
 +
@@ -76,11 +76,11 @@ If you are using an earlier version of {productname}, the error occurs because t
 [id="troubleshooting-502-push"]
 == Troubleshooting 502 Podman push errors 
 
-In some cases, the following error might be returned when using `podman push`: `Error: Error writing blob: Error initiating layer upload to /v2/repo/image/blobs/uploads/ in <registry>: received unexpected HTTP status: 502 Bad Gateway`. This issue is caused by either the Noobaa certificate rotation, or the service signing root CA rotation. The workaround for this issue is to manually add a new certificate chain to {productname}'s deployment after it has rotated. 
+In some cases, the following error might be returned when using `podman push`: `Error: Error writing blob: Error initiating layer upload to /v2/repo/image/blobs/uploads/ in <registry>: received unexpected HTTP status: 502 Bad Gateway`. This issue is caused by either the NooBaa certificate rotation, or the service signing root CA rotation. The workaround for this issue is to manually add a new certificate chain to {productname}'s deployment after it has rotated. 
 
 .Procedure 
 
-. Download the new certificate chain for your Noobaa endpoint by entering the following command:
+. Download the new certificate chain for your NooBaa endpoint by entering the following command:
 +
 [source,terminal]
 ----
@@ -121,7 +121,7 @@ For more information about this issue, see link:https://issues.redhat.com/browse
 [id="troubleshooting-502-unmanaged-storage"]
 == Troubleshooting 502 errors when using unmanaged storage
 
-In some cases, pulling an image from a {productname} registry that is using RadosGW or Noobaa as an unamanged object storage returns the following error: `parsing image configuration 502 (Bad Gateway):`. Use the following steps to resolve this issue. 
+In some cases, pulling an image from a {productname} registry that is using RadosGW or Noobaa as an unmanaged object storage returns the following error: `parsing image configuration 502 (Bad Gateway):`. Use the following steps to resolve this issue. 
 
 .Procedure 
 
@@ -145,7 +145,7 @@ DISTRIBUTED_STORAGE_PREFERENCE:
     - radosGWStorage
 ----
 
-.. If you are using Noobaa storage:
+.. If you are using NooBaa storage:
 +
 [source,yaml]
 ----
@@ -164,4 +164,4 @@ DISTRIBUTED_STORAGE_PREFERENCE:
   - default
 ----
 +
-With these updates, you should be able to successfully pull images when using unmanaged object storage.
+With these updates, you can successfully pull images when using unmanaged object storage.
diff --git a/modules/java-image-scan-not-working.adoc b/modules/java-image-scan-not-working.adoc
@@ -10,7 +10,7 @@ Use the following procedure to disable Java scanning from Clair.
 
 .Procedure 
 
-. Check which SHA ID errors out by reaching out to the Java/Maven indexer, for example:
+. Check which SHA ID errors out by reaching out to the Maven indexer, for example:
 +
 [source,terminal]
 ----
@@ -33,14 +33,14 @@ namespace | repo_name |                               sha_digest
 redhat    | quay      | sha256:0cea90e4778f9241c20421d8c97a8d182fd0fa51e6c84210dc4b57522fc901b8
 ----
 
-. Run the following command to find the base OS of the image, assuming it is Java-based:
+. Run the following command to find the base operating system of the image, assuming it is Java-based:
 +
 [source,terminal]
 ----
 $ podman run image:tag  /bin/bash -c "cat /etc/*release"
 ----
 
-. There are no documented steps to stop the Java/Maven indexer. Run the following command in a development or test cluster first, setting the API request to a page that returns a `404` so that it fails quickly:
+. There are no documented steps to stop the Maven indexer. Run the following command in a development or test cluster first, setting the API request to a page that returns a `404` so that it fails quickly:
 +
 [source,yaml]
 ----
diff --git a/modules/marathon-mesos-fail.adoc b/modules/marathon-mesos-fail.adoc
@@ -87,7 +87,7 @@ drwx------ root/root         0 2015-07-28 02:54 .docker/
 -rw------- root/root       114 2015-07-28 01:31 .docker/config.json
 ----
 
-. Optional. Put the tarball into a directory readably by Mesos:
+. Optional. Put the `.tar` file into a directory readably by Mesos:
 +
 [source,terminal]
 ----
diff --git a/modules/missing-runc-files.adoc b/modules/missing-runc-files.adoc
@@ -6,7 +6,7 @@ When attempting to start containers using the Podman client tool, users encounte
 
 The cause of this issue is the absence of required `runc` files in the older version of Podman. These missing files prevent the proper execution of containers, resulting in the encountered error. Updating Podman ensures that the necessary runc files are present, enabling the successful deployment of containers.
 
-To resolve this issue, it is recommended to update the Podman version in order to obtain the updated `runc` files. By updating Podman, the missing runc files will be installed, allowing containers to be deployed successfully.
+To resolve this issue, it is recommended to update the Podman version to obtain the updated `runc` files. By updating Podman, the missing runc files will be installed, allowing containers to be deployed successfully.
 
 Use the following command to update Podman:
 [source,terminal]
diff --git a/modules/running-quay-debug-mode.adoc b/modules/running-quay-debug-mode.adoc
@@ -29,7 +29,7 @@ Use the following procedure to run the {productname} Operator in debug mode.
 
 .Procedure 
 
-. Enter the following command to edit the `QuayRegistry` CRD:
+. Enter the following command to edit the `QuayRegistry` custom resource definition:
 +
 [source,terminal]
 ----
diff --git a/modules/storage-health-check-geo-repl.adoc b/modules/storage-health-check-geo-repl.adoc
diff --git a/modules/storage-troubleshooting-issues.adoc b/modules/storage-troubleshooting-issues.adoc
diff --git a/modules/troubleshooting-401-helm.adoc b/modules/troubleshooting-401-helm.adoc
diff --git a/modules/troubleshooting-slow-pushes.adoc b/modules/troubleshooting-slow-pushes.adoc
diff --git a/modules/unsupported-security-scan.adoc b/modules/unsupported-security-scan.adoc
diff --git a/troubleshooting_quay/master.adoc b/troubleshooting_quay/master.adoc

Original file line number	Diff line number	Diff line change
`@@ -14,4 +14,4 @@ The following authentication methods are supported by {productname}:`
`14`	`14`
`15`	`15`	`* Token-based authentication. Users can obtain unique tokens that grant access to specific resources within {productname}. Tokens can be obtained through various means, such as OAuth or by generating API tokens within the {productname} user interface. Token-based authentication is often used for automated or programmatic access to the registry.`
`16`	`16`
`17`		`-* External identity provider. {productname} can integrate with external identity providers, such as LDAP or AzureAD, for authentication purposes. This integration allows organizations to leverage their existing identity management infrastructure, enabling centralized user authentication and reducing the need for separate user databases.`
	`17`	`+* External identity provider. {productname} can integrate with external identity providers, such as LDAP or AzureAD, for authentication purposes. This integration allows organizations to use their existing identity management infrastructure, enabling centralized user authentication and reducing the need for separate user databases.`
Original file line number	Diff line number	Diff line change
@@ -6,4 +6,4 @@ When building an image, the following error is returned: `A build step failed: A
`6`	`6`
`7`	`7`	* The `.dockerignore` file contains the Dockerfile. Unlike Docker Hub, the Dockerfile is part of the Build Context on {productname}. The Dockerfile must not appear in the `.dockerignore` file. Remove the Dockerfile from the `.dockerignore` file to resolve the issue.
`8`	`8`
`9`		`-* The Build Trigger is incorrect. Verify the Dockerfile location and the branch/tag value specified in the Build Trigger.`
	`9`	`+* The build trigger is incorrect. Verify the Dockerfile location and the branch or tag value specified in the build trigger.`
Original file line number	Diff line number	Diff line change
`@@ -316,7 +316,7 @@ $ podman stats <container_name>`
`316`	`316`	`postgres=# \l+`
`317`	`317`	`----`
`318`	`318`
`319`		`-. Enter the following command to connect with the PostgreSQL database:`
	`319`	`+. Enter the following command to connect to the PostgreSQL database:`
`320`	`320`	`+`
`321`	`321`	`[source,terminal]`
`322`	`322`	`----`
Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,7 @@`
`4`	`4`
`5`	`5`	In some cases, using `docker pull` might return the following error: `39cb5a2eab5d: Error pulling image (myimage) from quay.io/my/repository. . . Could not find repository on any of the indexed registries.` There are two reasons for receiving this error.
`6`	`6`
`7`		`-* Linux kernel bug on Ubuntu Precise Pangolin (12.04 LTS) (64-bit). Precise has a Linux kernel bug that must be updated in order to use Docker. Use the following commands to update and reboot Precise.`
	`7`	`+* Linux kernel bug on Ubuntu Precise Pangolin (12.04 LTS) (64-bit). Precise has a Linux kernel bug that must be updated to use Docker. Use the following commands to update and reboot Precise.`
`8`	`8`	`+`
`9`	`9`	`[source,terminal]`
`10`	`10`	`----`
`@@ -21,7 +21,7 @@ $ sudo apt-get install linux-image-generic-lts-raring linux-headers-generic-lts-`
`21`	`21`	`$ sudo reboot`
`22`	`22`	`----`
`23`	`23`
`24`		`-* Missing AUFS on Raring 13.04 and Saucy 13.10 (64-bit). Not all installations of Ubuntu 13.04/13.10 ship with AUFS enabled. Enter the following commands to install additional Linux kernel modules:`
	`24`	`+* Missing AUFS on Raring 13.04 and Saucy 13.10 (64-bit). Not all installations of Ubuntu 13.04 or 13.10 include AUFS enabled. Enter the following commands to install additional Linux kernel modules:`
`25`	`25`	`+`
`26`	`26`	`[source,terminal]`
`27`	`27`	`----`
Original file line number	Diff line number	Diff line change
`@@ -12,7 +12,7 @@ To resolve this issue, you can increase the database connection count by using t`
`12`	`12`
`13`	`13`	. Navigate to your `/var/lib/pgsql/data/postgresql.conf` file.
`14`	`14`
`15`		-. Increase the database connection count by updating the the `max_connections` variable. It is recommended to set the number of connections on the database to at least `1000` for a development cluster, and `2000` for a production cluster. In some cases you might need more. For example:
	`15`	+. Increase the database connection count by updating the `max_connections` variable. It is recommended to set the number of connections on the database to at least `1000` for a development cluster, and `2000` for a production cluster. In some cases you might need more. For example:
`16`	`16`	`+`
`17`	`17`	`[source,yaml]`
`18`	`18`	`----`
Original file line number	Diff line number	Diff line change
`@@ -87,7 +87,7 @@ drwx------ root/root 0 2015-07-28 02:54 .docker/`
`87`	`87`	`-rw------- root/root 114 2015-07-28 01:31 .docker/config.json`
`88`	`88`	`----`
`89`	`89`
`90`		`-. Optional. Put the tarball into a directory readably by Mesos:`
	`90`	+. Optional. Put the `.tar` file into a directory readably by Mesos:
`91`	`91`	`+`
`92`	`92`	`[source,terminal]`
`93`	`93`	`----`
Original file line number	Diff line number	Diff line change
`@@ -29,7 +29,7 @@ Use the following procedure to run the {productname} Operator in debug mode.`
`29`	`29`
`30`	`30`	`.Procedure`
`31`	`31`
`32`		-. Enter the following command to edit the `QuayRegistry` CRD:
	`32`	+. Enter the following command to edit the `QuayRegistry` custom resource definition:
`33`	`33`	`+`
`34`	`34`	`[source,terminal]`
`35`	`35`	`----`