diff --git a/docs/guides/site-to-site-connectivity/end-customers.mdx b/docs/guides/site-to-site-connectivity/end-customers.mdx index 1403f58f8..7e291d752 100644 --- a/docs/guides/site-to-site-connectivity/end-customers.mdx +++ b/docs/guides/site-to-site-connectivity/end-customers.mdx @@ -12,7 +12,10 @@ tags: Your vendor wants to create a secure persistent connection between your network and theirs, which allows them to access and take action on your services and data. We call this [**site-to-site connectivity**](https://ngrok.com/use-cases/site-to-site-connectivity). -Your vendor will create the required configuration files and deployment strategy and share them with directly. You must contact with your vendor to request changes to that configuration, including those based on the content of this document. +Your vendor will create the required configuration files and deployment strategy +and share them with you directly. You must contact with your vendor to request +changes to that configuration, including those based on the content of this +document. ### What is ngrok? @@ -267,9 +270,10 @@ restart policy](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy) is set to `Always`. -ngrok releases security and feature updates through all our installation channels and package managers. Your vendor will - -. The process for updating your ngrok agent(s) depends on how you installed them +ngrok releases security and feature updates through all our installation +channels and package managers. Your vendor will work with you on when and how to +update your ngrok agent(s) because the process depends on how they asked you to +install them. - Package manager (`brew` or `apt`): Get updated agent versions through the same channel (e.g. `brew update && brew upgrade package_name` or `apt update && apt install ngrok`). - Binary from our [downloads page](https://ngrok.com/download): Follow the same process again or [update directly from your CLI](/docs/agent/#updates) with `ngrok update`.