diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx
index fa6d7c26ca0..6b9c1ecd041 100644
--- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx
+++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx
@@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY=<your-access-key>
 export BEACON_AGENT_PROJECT_ID=<your-project-id>
 ```
 
-Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory. using those environment variables.
+These environment variables are used when you run the `beacon-agent setup` command to create a configuration file in the Beacon configuration directory.
 
 You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location. 
 
@@ -153,7 +153,7 @@ provider:
     poll_interval: 5m0s
 ```
 
-## Test Beacon Agent locally.
+## Test Beacon Agent locally
 
 For an initial test of the agent, you can get it to send the data that it would normally send to the EDB Enterprise AI control plane to standard output, your terminal session, instead. This allows you to quickly confirm if the agent is successfully able to gather data and what that data looks like.
 
@@ -210,7 +210,7 @@ agent:
 
 ```
 
-## Run Beacon Agent.
+## Run Beacon Agent
 
 Run the agent using the following command: