diff --git a/product_docs/docs/pem/10/registering_agent.mdx b/product_docs/docs/pem/10/registering_agent.mdx
index a98b457e999..0f2f33fddb0 100644
--- a/product_docs/docs/pem/10/registering_agent.mdx
+++ b/product_docs/docs/pem/10/registering_agent.mdx
@@ -117,9 +117,13 @@ The following are some advanced options for PEM agent registration.
 
 Each registered PEM agent must have a unique agent ID. The value `max(id)+1` is assigned to each agent ID unless a value is provided using the `-o` options as shown [in these examples](#overriding-default-configurations---examples).
 
+### Setting other agent configuration parameters
+
+The `-o` command line option allows you to override other agent configuration parameters during registration. For the complete list of these configuration parameters please refer to [this page](/pem/latest/managing_pem_agent/modifying_agent_configuration/).
+
 ### Overriding default configurations - examples
 
-This example shows how to register the PEM agent and override the default configurations.
+These examples show how to register the PEM agent and override the default configurations.
 
 #### Setting the agent ID
 
@@ -259,4 +263,4 @@ To use a non-root user account to register a PEM agent, you must first install t
 !!! Note
     - Any probes and jobs that require root permission or access to a file owned by another user (for example,  enterprisedb) fail. 
     - If you move the `agent.cfg` file from its default location to another, the PEM dashboard might display the agent status as `unknown`. See [Troubleshooting agent issues](troubleshooting_agent/#updating-configuration-file-path-agent-status-displaying-as-unknown) for more information.
-    
\ No newline at end of file
+