docs(self-hosted): note about relay version to be exact/similar with self-hosted version

Author: aldy505

develop-docs/self-hosted/reference-architecture/separate-ingest-box.mdx

@@ -6,7 +6,7 @@ sidebar_order: 2
 
 Other than having a [separate domain](/self-hosted/experimental/reverse-proxy/#expose-only-ingest-endpoint-publicly) to view the web UI and ingest data, you can also put a separate box (or server) for ingesting data, and have it relay data to the main box. This setup is recommended for high-traffic installations, and environment where you have multiple data centers.
 
-Using this setup also prevents DDOS attacks, since we assume your main box can only be accessed using some kind of VPN. If there are any invalid payload being sent to your Relay instance, it will be dropped immediately. If your main box is not reachable, your Relay will keep retrying to send the data.
+Using this setup also prevents DDOS attacks against your Sentry installation, since we assume your main box can only be accessed using some kind of VPN. If there are any invalid payload being sent to your Relay instance, it will be dropped immediately. If your main box is not reachable, your Relay will keep retrying to send the data.
 
 Please note that you don't need to have multiple data centers in different countries/regions. The region naming on the diagram is to make it easier to understand.
 
@@ -44,7 +44,7 @@ graph TB
   internet3 --> relay3 -- Through VPN tunnel --> main
 ```
 
-To configure the relay, you can install Sentry Relay on your machine through the [Relay Getting Started Guide](https://docs.sentry.io/product/relay/getting-started/). You should configure the Relay to run on `proxy` mode, and point it to the main Sentry server. You can also configure it to use a different port, or a different protocol (HTTP or HTTPS).
+To configure the relay, you can install Sentry Relay on your machine through the [Relay Getting Started Guide](https://docs.sentry.io/product/relay/getting-started/). You should configure the Relay to run on `proxy` mode, and point it to the main Sentry server. You can also configure it to use a different port, or a different protocol (HTTP or HTTPS). Make sure you are using the same version of your self-hosted Sentry version.
 
 A simple configuration for the relay would be:
 
@@ -78,6 +78,7 @@ sentry:
   dsn: "https://[email protected]/1"
 ```
 
+Always remember to upgrade the Relay whenever you upgrade your self-hosted Sentry instance.
 
 <Alert level="info" title="Fun Fact">
   Sentry SaaS use this similar setup for their ingestion servers, behind Google Anycast IP address.