example command to write PD conf entry

website/content/docs/connect/proxies/deploy-service-mesh-proxies.mdx

@@ -30,7 +30,11 @@ If you want to define global passthrough settings for all Envoy proxies, create
    - `Kind`: Must be set to `proxy-defaults`
    - `Name`: Must be set to `global`
 1. Configure any additional settings you want to apply to all proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for details about all settings available in the configuraiton entry. 
-1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write). 
+1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write). The following example writes a proxy defaults configuration entry from a local HCL file using the CLI:
+
+```shell-session
+$ consul config write proxy-defaults.hcl
+```
 
 ## Define service mesh proxy 
 

website/content/docs/connect/proxies/deploy-sidecar-services.mdx

@@ -33,7 +33,11 @@ If you want to define global passthrough settings for all Envoy proxies, create
    - `Kind`: Must be set to `proxy-defaults`
    - `Name`: Must be set to `global`
 1. Configure any additional settings you want to apply to all proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for details about all settings available in the configuraiton entry. 
-1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write). 
+1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write). The following example writes a proxy defaults configuration entry from a local HCL file using the CLI:
+
+```shell-session
+$ consul config write proxy-defaults.hcl
+```
 
 ## Define service mesh proxy 
 

website/content/docs/connect/proxies/index.mdx

@@ -1,6 +1,6 @@
 ---
 layout: docs
-page_title: Service Mesh Proxy Overview
+page_title: Service mesh proxy overview
 description: >-
   In Consul service mesh, each service has a sidecar proxy that secures connections with other services in the mesh without modifying the underlying application code. You can use the built-in proxy, Envoy, or a custom proxy to handle communication and verify TLS connections.
 ---
@@ -32,7 +32,7 @@ Consul has first-class support for Envoy proxies, which is a highly configurable
 - [Envoy proxy reference](/consul/docs/connect/proxies/envoy)
 - [Envoy API documentation](https://www.envoyproxy.io/docs/envoy/v1.17.2/api-docs/xds_protocol)
 
-You can use Consul's built-in proxy service that supports L4 network traffic, which is suitable for testing and development but not recommended for production environments. Refer to the [built-in proxy reference](/consul/docs/connect/proxies/builtin) for additional information.
+You can use Consul's built-in proxy service that supports L4 network traffic, which is suitable for testing and development but not recommended for production environments. Refer to the [built-in proxy reference](/consul/docs/connect/proxies/built-in) for additional information.
 
 ## Workflow
 

website/content/docs/connect/proxies/proxy-config-reference.mdx

@@ -1,6 +1,6 @@
 ---
 layout: docs
-page_title: Service mesh proxy configuration
+page_title: Service mesh proxy configuration reference
 description: >-
   You can register a service mesh sidecar proxy separately from the registration of the service instance it fronts. Learn about proxy configuration options and how to format them with examples.
 ---