docs: Remove incorrect references to chat.zulip.org.

Most of these are Help Center links that should be pointing to the
production Help Center.

docs/documentation/user.md

@@ -23,7 +23,7 @@ in-product, so it's important to keep the docs up to date.
 ## Editing and testing
 
 The user documentation is available under `/help/` on any Zulip server;
-(e.g. <https://chat.zulip.org/help/> or `http://localhost:9991/help/` in
+(e.g. <https://zulip.com/help/> or `http://localhost:9991/help/` in
 the Zulip development environment). The user documentation is not hosted on
 ReadTheDocs, since Zulip supports running a server completely disconnected
 from the Internet, and we'd like the documentation to be available in that

docs/overview/gsoc-ideas.md

@@ -298,7 +298,7 @@ CSS](https://github.com/zulip/zulip/).
   would be great to demonstrate as part of an application.  The
   [Zulip integration writing guide](../documentation/integrations.md)
   and
-  [integration documentation](https://chat.zulip.org/integrations/)
+  [integration documentation](https://zulip.com/integrations/)
   are useful materials for learning about how things currently work,
   and
   [the integrations label on GitHub](https://github.com/zulip/zulip/labels/area%3A%20integrations)
@@ -307,7 +307,7 @@ CSS](https://github.com/zulip/zulip/).
 
 - Build a meta-integration that converts the Slack incoming webhook
   API to post messages into Zulip. Zulip has several dozen native
-  integrations (https://chat.zulip.org/integrations/), but Slack has a
+  integrations (https://zulip.com/integrations/), but Slack has a
   ton more.  We should build an interface to make all of Slack’s
   numerous third-party integrations work with Zulip as well, by
   basically building a Zulip incoming webhook interface that accepts

docs/production/maintain-secure-upgrade.md

@@ -38,4 +38,4 @@ Moved to [Management commands](../production/management-commands.md).
 
 ### API and your Zulip URL
 
-Moved to [REST API](https://chat.zulip.org/api/rest).
+Moved to [REST API](https://zulip.com/api/rest).

docs/subsystems/client.md

@@ -12,9 +12,8 @@ of Zulip; it's primarily intended to assist debugging.
 ## Analytics
 
 A `Client` is used to sort messages into client categories such as
-`ZulipElectron` on the `/stats`
-[page](https://chat.zulip.org/stats). For more information see,
-[Analytics](analytics.md).
+`ZulipElectron` on the `/stats` page. For more information see,
+[Analytics](../subsystems/analytics.md).
 
 ## Integrations
 

docs/tutorials/new-feature-tutorial.md

@@ -647,9 +647,9 @@ behavior of the setting you just created.
 After you add a new view, you should document your feature. This
 feature adds new functionality that requires messages to have topics
 if the setting is enabled. A recommended way to document this feature
-would be to update and/or augment
-[Zulip's user documentation](https://chat.zulip.org/help/)
-to reflect your changes and additions.
+would be to update and/or augment [Zulip's user
+documentation](https://zulip.com/help/) to reflect your changes and
+additions.
 
 At the very least, this will involve adding (or modifying) a Markdown file
 documenting the feature to `templates/zerver/help/` in the main Zulip

zerver/data_import/slack.py

@@ -180,7 +180,7 @@ def users_to_zerver_userprofile(slack_data_dir: str, users: List[ZerverFieldsT],
             user_id = user_id_count
 
         email = get_user_email(user, domain_name)
-        # ref: https://chat.zulip.org/help/change-your-profile-picture
+        # ref: https://zulip.com/help/change-your-profile-picture
         avatar_url = build_avatar_url(slack_user_id, user['team_id'],
                                       user['profile']['avatar_hash'])
         build_avatar(user_id, realm_id, email, avatar_url, timestamp, avatar_list)