diff --git a/en/docs/api-design-manage/design/advanced-topics/adding-an-api-state-change-workflow.md b/en/docs/api-design-manage/design/advanced-topics/adding-an-api-state-change-workflow.md
index 2518471b2a..2ce4197f26 100644
--- a/en/docs/api-design-manage/design/advanced-topics/adding-an-api-state-change-workflow.md
+++ b/en/docs/api-design-manage/design/advanced-topics/adding-an-api-state-change-workflow.md
@@ -93,6 +93,6 @@ The elements of the above configuration are explained belo
|----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `processDefinitionKey` | Mandatory | Business Process Modeling Notation (BPMN) process definition ID. BPMN process provided with AM as default has `APIStateChangeApprovalProcess` as the ID. |
| `stateList` | Mandatory | This is a comma-separated list of the current state and intended action. For example, Created:Publish,Published:Block |
-| `serviceEndpoint` | Optional | The URL of the BPMN process engine. This overrides the global `` value from the `api-manager.xml` file. This can be used to connect a separate workflow engine for a tenant. |
-| `username` | Optional | Username for the external BPMN process engine. This overrides the value of the `` element that is defined in the `api-manager.xml` file of the tenant. |
-| `password` | Optional | Password for the external BPMN process engine. This overrides the value of the `` element that is defined in the `api-manager.xml` file of the tenant. |
+| `serviceEndpoint` | Optional | The URL of the BPMN process engine. This overrides the global workflow engine URL configured for the server (from `deployment.toml`). This can be used to connect a separate workflow engine for a tenant. |
+| `username` | Optional | Username for the external BPMN process engine. This overrides the global workflow engine username configured for the server (from `deployment.toml`). |
+| `password` | Optional | Password for the external BPMN process engine. This overrides the global workflow engine password configured for the server (from `deployment.toml`). |
diff --git a/en/docs/reference/faq.md b/en/docs/reference/faq.md
index 649d400d95..39be4d978f 100644
--- a/en/docs/reference/faq.md
+++ b/en/docs/reference/faq.md
@@ -201,28 +201,7 @@ username = "admin"
password = "${new-password}"
```
-You can verify whether the password change is applied correctly by checking the following elements in the `/repository/conf/api-manager.xml` file.
-
-``` xml
-
- admin
- newpassword
-
-```
-
-``` xml
-
- admin
- newpassword
-
-```
-
-``` xml
-
- admin
- newpassword
-
-```
+You can verify whether the password change is applied correctly by checking the updated `deployment.toml` values and signing in with the new credentials. The server renders runtime XML from these settings at startup, so you should not edit `api-manager.xml` directly.
Go to the **Resources > Browse** menu in the management console to open the registry and update the credentials in the `/_system/governance/apimgt/applicationdata/sign-up-config.xml` registry location.
### How can I manage session timeouts for the management console?