Updated the analytics origin documentation for the Website service target.

Scripts/bootstrap

@@ -194,9 +194,9 @@ Next steps:
        - $W/Resources/Static/site.webmanifest                 (name / short_name)
   2. Set a real database password in a git-ignored $W/.env
      (the committed .env.local defaults the password to the slug — do NOT ship that).
-  3. Analytics ships OFF, and stays off until you opt in. To enable it: point
-     String.Analytics.origin at your own Umami instance (it defaults to the
-     reserved https://analytics.example.com), allow that origin in
+  3. Analytics ships OFF, and stays off until you opt in. To enable it: check
+     String.Analytics.origin (it defaults to the platform instance at
+     https://analytics.rock-n-code.com), allow that origin in
      security.contentSecurityPolicy, then set ANALYTICS_WEBSITE_ID.
   4. Point the git remote at your new repository:
        git remote set-url origin <new-repo-url>     # or 'git remote add origin ...'