From 6a3ad079adc073e9372ae8377b6a21ce4080e482 Mon Sep 17 00:00:00 2001
From: Ian Fowler <ifowler@redhat.com>
Date: Tue, 21 May 2024 08:42:29 +0100
Subject: [PATCH] Changes to Controller Admin

Updated attributes

Controller Admin Guide UI updates chapters 11-20

https://issues.redhat.com/browse/AAP-23677
---
 .../modules/platform/proc-controller-api-4xx-error-config.adoc  | 2 +-
 .../platform/proc-controller-configure-usability-analytics.adoc | 2 +-
 downstream/modules/platform/proc-controller-set-up-logging.adoc | 2 +-
 downstream/modules/platform/ref-controller-loggers.adoc         | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/downstream/modules/platform/proc-controller-api-4xx-error-config.adoc b/downstream/modules/platform/proc-controller-api-4xx-error-config.adoc
index 6d8a58438..e7068ede1 100644
--- a/downstream/modules/platform/proc-controller-api-4xx-error-config.adoc
+++ b/downstream/modules/platform/proc-controller-api-4xx-error-config.adoc
@@ -14,7 +14,7 @@ These messages can be configured as required.
 Use the following procedure to modify the default API 4XX errors log message format.
 
 .Procedure
-. From  the navigation panel, select menu:{MenuAEAdminSettings}[Logging].
+. From  the navigation panel, select {MenuSetLogging}.
 . On the *Logging settings* page, click btn:[Edit].
 . Modify the field *Log Format For API 4XX Errors*.
 
diff --git a/downstream/modules/platform/proc-controller-configure-usability-analytics.adoc b/downstream/modules/platform/proc-controller-configure-usability-analytics.adoc
index 0ebc75916..2b57a381a 100644
--- a/downstream/modules/platform/proc-controller-configure-usability-analytics.adoc
+++ b/downstream/modules/platform/proc-controller-configure-usability-analytics.adoc
@@ -13,7 +13,7 @@ Only users installing a trial of {PlatformName} or a fresh installation of {Cont
 .Procedure
 
 . From the navigation panel, select {MenuSetSystem}.
-. Click btn:[Edit].
+. On the *System Settings* page, click btn:[Edit].
 . Select the *Gather data for {Analytics}* checkbox.
 . Enter the following information:
 * *Last gather data for {Analytics}*: Set the date and time.
diff --git a/downstream/modules/platform/proc-controller-set-up-logging.adoc b/downstream/modules/platform/proc-controller-set-up-logging.adoc
index c395c165f..43941cb4e 100644
--- a/downstream/modules/platform/proc-controller-set-up-logging.adoc
+++ b/downstream/modules/platform/proc-controller-set-up-logging.adoc
@@ -5,7 +5,7 @@
 Use the following procedure to set up logging to any of the aggregator types.
 
 .Procedure
-. From the navigation panel, select menu:{MenuAEAdminSettings}[Logging].
+. From the navigation panel, select {MenuSetLogging}.
 . On the *Logging settings* screen, click btn:[Edit].
 . Set the following configurable options:
 
diff --git a/downstream/modules/platform/ref-controller-loggers.adoc b/downstream/modules/platform/ref-controller-loggers.adoc
index 83638e207..a5b10b872 100644
--- a/downstream/modules/platform/ref-controller-loggers.adoc
+++ b/downstream/modules/platform/ref-controller-loggers.adoc
@@ -15,4 +15,4 @@ These loggers only use the log-level of `INFO`, except for the `awx` logger, whi
 Additionally, the standard {ControllerName} logs are deliverable through this same mechanism.
 It should be apparent how to enable or disable each of these five sources of data without manipulating a complex dictionary in your local settings file, and how to adjust the log-level consumed from the standard {ControllerName} logs.
 
-From the navigation panel, select menu:{MenuAEAdminSettings}[Logging]. You can configure the logging components in the *Logging settings* page.
+From the navigation panel, select {MenuSetLogging}. You can configure the logging components in the *Logging settings* page.