diff --git a/deploy_quay_on_openshift_op_tng/master.adoc b/deploy_quay_on_openshift_op_tng/master.adoc
index 924f6ec9f..f9c679214 100644
--- a/deploy_quay_on_openshift_op_tng/master.adoc
+++ b/deploy_quay_on_openshift_op_tng/master.adoc
@@ -125,7 +125,7 @@ include::modules/georepl-deploy-operator.adoc[leveloffset=+3]
 include::modules/georepl-mixed-storage.adoc[leveloffset=+3]
 
 include::modules/backing-up-and-restoring-intro.adoc[leveloffset=+1]
-include::modules/backing-up-red-hat-quay.adoc[leveloffset=+2]
+include::modules/backing-up-red-hat-quay-operator.adoc[leveloffset=+2]
 include::modules/restoring-red-hat-quay.adoc[leveloffset=+2]
 
 include::modules/operator-ipv6-dual-stack.adoc[leveloffset=+1]
diff --git a/modules/rn_3_80.adoc b/modules/rn_3_80.adoc
index 50f964d9f..b7fc52c9a 100644
--- a/modules/rn_3_80.adoc
+++ b/modules/rn_3_80.adoc
@@ -161,6 +161,8 @@ For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4588[PR
 
 * There is a known issue when using the `FEATURE_SUPERUSERS_FULL_ACCESS` configuration field with the {productname} UI v2. When this field is set, all superuser actions on tenant content should be audited. Currently, when a superuser deletes an existing organization that is owned by a normal user, there is no way to audit that operation. This will be fixed in a future version of {productname}.
 
+* There is a known issue when using the `FEATURE_SUPERUSERS_FULL_ACCESS` configuration field with the {productname} UI v2. When setting this field to `true` in your config.yaml file, {productname} superusers can view organizations created by normal users, but cannot see the image repository. As a temporary workaround, superusers can view those repositories by navigating to them from the *Organizations* page. This will be fixed in a future version of {productname}. 
+
 * When running {productname} in the old UI, timed-out sessions would require that a superuser input their password again in the pop-up window. With the new UI, superusers are returned to the main page and required to input their username and password credentials. This is a known issue and will be fixed in a future version of the new UI. 
 
 [id="ipv6-limitations-38"]
@@ -180,6 +182,11 @@ For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4470[PR
 
 * Currently, Github and link:api.github.com[api.github.com] do not support IPv6. When {productname} is deployed on {ocp} with IPv6 enabled, the config editor cannot be configured to use Github authentication. 
 
+[id="bug-fixes-38"]
+=== {productname} bug fixes
+
+* link:https://issues.redhat.com/browse/PROJQUAY-4431[PROJQUAY-4431]. Proxy cache failed to validate Azure Container Registry(ACR). 
+
 [id="quay-feature-tracker"]
 === {productname} feature tracker