From b71d2972303c1821bc043e0f16378aac33cc3011 Mon Sep 17 00:00:00 2001
From: Robert <17119716+robmonte@users.noreply.github.com>
Date: Fri, 28 Feb 2025 13:15:47 -0600
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: vinay-gopalan <86625824+vinay-gopalan@users.noreply.github.com>
---
 website/content/docs/sync/index.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/sync/index.mdx b/website/content/docs/sync/index.mdx
index 6c9474de07b9..1bf20b0c0cf8 100644
--- a/website/content/docs/sync/index.mdx
+++ b/website/content/docs/sync/index.mdx
@@ -254,13 +254,13 @@ for each destination type below:
 ### Endpoint security
 
 By default, Vault restricts the allowed IP addresses and port numbers used by the sync clients to safeguard against
-server-side request forgery (SSRF). All special purpose IP's defined at the IANA special-purpose registry for 
+server-side request forgery (SSRF). All special purpose IPs defined at the IANA special-purpose registry for 
 [IPv4](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml) and
 [IPv6](https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml) are blocked, while the only
 two allowed ports are 80 and 443.
 
 Both IP addresses and port numbers can be customized to fit the specific needs of the environment. This is useful in environments such
-as when the destination service is behind things such as a private endpoint, a load balancer, or a proxy. This strict networking policy
+where the destination service is behind things such as a private endpoint, a load balancer, or a proxy. This strict networking policy
 can also be entirely disabled in environments where IP addresses or port numbers are not static values.
 Refer to the [API](#api) section for more information on these parameters.