Apply suggestions from code review

Co-authored-by: Daniela Merlo <97902112+dmerlob@users.noreply.github.com>

Author: failup

modules/ROOT/pages/godaddy-ans-registration.adoc

@@ -15,33 +15,33 @@ With GoDaddy ANS integration in API Manager, you can:
 * Track verification progress directly from API Manager
 * View verification status in Anypoint Exchange
 
-== Registration workflow
+== Registration Workflow
 
 The registration workflow spans API Manager, GoDaddy, and your DNS provider.
 
-You initiate registration from an API instance in API Manager. GoDaddy validates domain ownership using standard verification methods such as DNS or ACME challenges. API Manager tracks the verification process and updates the agent status when verification is complete.
+Initiate registration from an API instance in API Manager. GoDaddy validates domain ownership using standard verification methods such as DNS or ACME challenges. API Manager tracks the verification process and updates the agent status when verification is complete.
 
 Depending on your domain configuration, some steps might require manual action.
 
-== Consumer endpoint and FQDN
+== Consumer Endpoint and FQDN
 
 The consumer endpoint configured for the agent is used to derive a fully qualified domain name (FQDN) that uniquely identifies the agent.
 
-Only the hostname portion of the endpoint is used. For example, in `https://example.com/path`, the registered domain is `example.com`.
+Only the hostname of the endpoint is used. For example, in `https://example.com/path`, the registered domain is `example.com`.
 
-This domain is registered as part of the verification process and cannot be modified after registration.
+This domain is registered as part of the verification process and can't be modified after registration.
 
 For more information, see https://www.godaddy.com/resources/skills/whats-a-fully-qualified-domain-name-fqdn-and-whats-it-good-for[What is a Fully Qualified Domain Name (FQDN)?].
 
-== Domain requirements
+== Domain Requirements
 
-The domain used for registration must meet the following requirements:
+The domain used for registration must meet these requirements:
 
-* Must be a custom domain (vanity domain)
-* MuleSoft-managed domains such as `cloudhub.io` are not supported
-* Must be associated with a valid DNS configuration
+* Be a custom domain (vanity domain)
+* Not be a MuleSoft-managed domain such as `cloudhub.io`, as these domains aren’t supported
+* Be associated with a valid DNS configuration
 
-If these requirements are not met, registration cannot proceed.
+If these requirements aren't met, registration can't proceed.
 
 == Integration with Anypoint Exchange
 
@@ -50,11 +50,11 @@ Verification status is reflected in Anypoint Exchange:
 * Verified agents display a visual indicator in search results and asset pages
 * Verification is tied to the agent instance and its associated domain
 
-== Next steps
+== Next Steps
 
 Before registering an agent, ensure that your environment is properly configured.
 
-For more information, see xref:godaddy-set-up.adoc[Prepare your environment for agent verification].
+For more information, see xref:godaddy-set-up.adoc[Prepare Your Environment for Agent Verification].
 
 == See also
 

modules/ROOT/pages/godaddy-register-agent.adoc

@@ -1,4 +1,4 @@
-= Create an agent instance
+= Create an Agent Instance
 
 Create an agent instance in API Manager to expose your agent and configure its runtime, endpoint, and routing settings.
 
@@ -12,7 +12,7 @@ Before you begin, make sure that:
 * You have access to a target runtime (for example, Flex Gateway)
 * You have the required permissions to manage API instances
 
-== Create an agent instance
+== Create an Agent Instance
 
 . In Anypoint Platform, go to *API Manager*.
 . Click *Add new instance*.
@@ -36,7 +36,7 @@ This endpoint is used to derive the domain that identifies the agent during veri
 
 After deployment, the agent instance is created and available in API Manager.
 
-== Next steps
+== Next Steps
 
 After creating the agent instance:
 
@@ -46,4 +46,4 @@ After creating the agent instance:
 
 Before verification, ensure that your environment is properly configured.
 
-For more information, see xref:godaddy-set-up.adoc[Prepare your environment for agent verification]
+For more information, see xref:godaddy-set-up.adoc[Prepare Your Environment for Agent Verification]

modules/ROOT/pages/godaddy-set-up.adoc

@@ -1,29 +1,29 @@
-= Prepare your environment for agent verification
+= Prepare Your Environment for Agent Verification
 
-Before verifying an agent using GoDaddy Agent Name Service (ANS), you must configure your environment to support domain-based identity validation.
+Before verifying an agent using GoDaddy Agent Name Service (ANS), configure your environment to support domain-based identity validation.
 
 Verification requires a custom domain, a configured runtime environment, and secure communication settings.
 
-== Custom domain
+== Custom Domain
 
 Agent verification requires a custom domain (vanity domain) that you own and control.
 
 * The domain associated with your agent must match the consumer endpoint used during registration.
-* The domain is used to establish the agent’s identity
-* You must be able to create and manage DNS records for the domain
-* MuleSoft-managed domains such as `cloudhub.io` are not supported
+* The domain is used to establish the agent’s identity.
+* You must be able to create and manage DNS records for the domain.
+* MuleSoft-managed domains such as `cloudhub.io` are not supported.
 
-== Private space
+== Private Space
 
-Agents must be deployed in a private space that supports custom domains and TLS configuration.
+Deploy agents in a private space that supports custom domains and TLS configuration.
 
-If you do not already have a private space, create one in Runtime Manager before proceeding.
+If you don't already have a private space, create one in Runtime Manager before proceeding.
 
 For more information, see xref:cloudhub-2::ps-manage.adoc[Private Spaces].
 
-== TLS context
+== TLS Context
 
-A TLS context must be configured in your private space for the domain used by the agent.
+Configure a TLS context in your private space for the domain used by the agent.
 
 TLS configuration enables secure communication and is required to complete verification. A TLS context must be configured for the domain used by the agent.
 
@@ -43,11 +43,11 @@ Make sure that:
 * The certificate is valid and active
 * The domain matches the consumer endpoint used by the agent
 
-If no TLS context is configured, verification cannot proceed and an error is displayed.
+If no TLS context is configured, verification can't proceed and an error is displayed.
 
 For more information, see xref:cloudhub-2::ps-config-domains.adoc[Configure domains and TLS certificates]
 
-== Gateway configuration
+== Gateway Configuration
 
 Agents must be exposed through a configured gateway to support domain-based verification.
 
@@ -67,7 +67,7 @@ Each agent must be configured with a separate endpoint in the gateway.
 If multiple agents are deployed on the same domain, each one requires its own explicit endpoint configuration.
 ====
 
-== Secret group access
+== Secret Group Access
 
 Agent verification requires access to a secret group in Secrets Manager.
 
@@ -78,11 +78,11 @@ Make sure that:
 * At least one secret group exists
 * You have permission to write to the selected secret group
 
-If you do not have the required permissions, you cannot complete verification.
+If you don't have the required permissions, you can't complete verification.
 
-IMPORTANT: If the domain, TLS context, and gateway configuration are not aligned, agent verification cannot be completed.
+IMPORTANT: If the domain, TLS context, and gateway configuration aren't aligned, agent verification can't be completed.
 
-== Next steps
+== Next Steps
 
 After completing the environment setup:
 

modules/ROOT/pages/godaddy-verify-agent.adoc

@@ -1,10 +1,10 @@
-= Verify an agent using GoDaddy ANS
+= Verify an Agent Using Godaddy Ans
 
 Verify an agent to establish a trusted identity based on domain ownership and enable its verified status in Anypoint Exchange.
 
 Verification uses GoDaddy Agent Name Service (ANS) to validate the domain associated with the agent and confirm that you control it.
 
-== Before you begin
+== Before You Begin
 
 Before verifying an agent, make sure that:
 
@@ -16,31 +16,31 @@ Before verifying an agent, make sure that:
 
 For infrastructure requirements such as domain configuration and TLS setup, see xref:godaddy-set-up.adoc[Prepare your environment for agent verification].
 
-== Start agent verification
+== Start Agent Verification
 
 . In Anypoint Platform, go to *API Manager*.
 . Select the API instance that represents your agent.
 . Click *Actions* > *Verify agent identity*.
 
 The verification wizard opens and guides you through the required steps.
 
-== Step 1: Provide prerequisites
+== Step 1: Provide Prerequisites
 
 In this step:
 
 * Confirm or update the *Consumer endpoint*
 +
-The consumer endpoint is used to derive the domain that will be verified. Only the hostname is used. This domain becomes part of the agent’s identity and cannot be changed after registration.
+The consumer endpoint is used to derive the domain that is verified. Only the hostname is used. This domain becomes part of the agent’s identity and can't be changed after registration.
 
 * Select a *Secret group*
 +
 The secret group is used to store credentials and generated security artifacts required for verification.
 
 You must have access to at least one secret group with sufficient permissions to continue. 
 
-If the domain or environment is not correctly configured, validation errors are displayed and you cannot proceed.
+If the domain or environment isn't correctly configured, validation errors are displayed and you can't proceed.
 
-== Step 2: Enter GoDaddy ANS credentials
+== Step 2: Enter GoDaddy ANS Credentials
 
 Provide your GoDaddy credentials:
 
@@ -51,7 +51,7 @@ These credentials are used to authenticate with GoDaddy ANS and initiate the ver
 
 If you don’t already have these credentials, generate them in your GoDaddy account.
 
-== Step 3: Verify domain ownership (ACME)
+== Step 3: Verify Domain Ownership (Acme)
 
 To prove domain ownership, create a DNS TXT record using the provided values.
 
@@ -61,9 +61,10 @@ To prove domain ownership, create a DNS TXT record using the provided values.
 
 API Manager checks whether the record has been propagated and validated.
 
-NOTE: ACME records expire after a limited time. If they expire, new records are generated automatically when you retry verification.
+[NOTE] 
+ACME records expire after a limited time. If they expire, new records are generated automatically when you retry verification.
 
-== Step 4: Verify DNS records
+== Step 4: Verify DNS Records
 
 After ACME verification, additional DNS records are generated.
 
@@ -73,7 +74,7 @@ After ACME verification, additional DNS records are generated.
 
 These records enable secure communication and complete the verification process.
 
-== Verification process
+== Verification Process
 
 Verification is asynchronous and depends on DNS propagation and external validation.
 
@@ -83,15 +84,15 @@ Verification is asynchronous and depends on DNS propagation and external validat
 
 You can close the verification dialog and return later. The status continues to update in the background.
 
-== Retry or restart verification
+== Retry or Restart Verification
 
-If verification is not completed:
+If verification isn't completed:
 
-* DNS records may expire after a limited time
+* DNS records can expire after a limited time
 * You can restart the verification process from the agent instance
 * New DNS records are generated when restarting
 
-== After verification
+== After Verification
 
 When verification is successful: