Update frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx

Co-authored-by: Raquel Smith <[email protected]>

frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx

@@ -66,16 +66,15 @@ export const OnboardingReverseProxy = ({ stepKey }: { stepKey: OnboardingStepKey
             }
         >
             <div className="mb-6 mt-6">
-                <p>A reverse proxy allows you to send events to PostHog Cloud using your own domain.</p>
+                <p>A reverse proxy allows you to retrieve flag information from PostHog Cloud using your own domain.</p>
                 <p>
-                    This means that events are sent from your own domain and are less likely to be intercepted by
-                    tracking blockers. You'll be able to capture more usage data without having to self-host PostHog.
+                    Network calls to and from your own domain and are less likely to be intercepted by
+                    tracking blockers. With a reverse proxy, all your users will be exposed to the flag 
+                    variants you intend. (Plus, you'll get more accurate event tracking, too!)
                 </p>
                 <p>
-                    Setting up a reverse proxy means setting up a service to redirect requests from a subdomain you
-                    choose (like <span className="font-mono break-keep">e.yourdomain.com</span>) to PostHog. It is best
-                    practice to use a subdomain that does not include posthog, analytics, tracking, or other similar
-                    words.
+                    This step is optional, especially as you are getting started. If you aren't the 
+                    right person to set this up, invite a team member to do it for you.
                 </p>
                 <h3>Documentation</h3>
                 <p>Here are some popular reverse proxy options:</p>