Corrected assumptions that Off-Topic = default channel (#7715)

source/collaborate/channel-types.rst

@@ -21,7 +21,7 @@ There are 5 types of channels in Mattermost:
 Public channels
 ---------------
 
-Public channels are open to everyone on a team and are identified with a **Globe** |globe| icon. New team members are automatically added to two public channels when they sign up: **Town Square** and **Off-Topic**.
+Public channels are open to everyone on a team and are identified with a **Globe** |globe| icon. New team members are automatically added to the **Town Square**  channel.
 
 See the :doc:`Join and leave channels </collaborate/join-leave-channels>` documentation for details on discovering, joining, and leaving other channels.
 

source/collaborate/collaborate-within-channels.rst

@@ -9,13 +9,10 @@ Channels are where you connect, collaborate, and communicate with your team abou
 You're added to default channels automatically
 ----------------------------------------------
 
-Everyone who joins a Mattermost :doc:`workspace </guides/use-mattermost>` is automatically added to two default public channels: **Town Square** and **Off-Topic**. See our :doc:`Channel Types </collaborate/channel-types>` documentation for details.
-
-- **Town Square** is great for your team-wide communications, such as announcements.
-- **Off-Topic** is great for fun, social, non-work-related conversations.
+Everyone who joins a Mattermost :doc:`workspace </guides/use-mattermost>` is automatically added to the **Town Square** channel. See our :doc:`Channel Types </collaborate/channel-types>` documentation for details.
 
 .. note::
-  Town Square can't be :ref:`archived <collaborate/archive-unarchive-channels:archive a channel>` or :doc:`converted to a private channel </collaborate/convert-public-channels>`, and users can't :ref:`leave <collaborate/join-leave-channels:leave a channel>` this default channel.
+  The Town Square channel can't be :ref:`archived <collaborate/archive-unarchive-channels:archive a channel>` or :doc:`converted to a private channel </collaborate/convert-public-channels>`, and users can't :ref:`leave <collaborate/join-leave-channels:leave a channel>` this default channel.
 
 Channel sidebar
 ----------------

source/collaborate/join-leave-channels.rst

@@ -74,7 +74,7 @@ When you leave a private channel, you must be re-added by another channel member
 
 .. note::
 
-  All users are added to the **Off-Topic** and **Town Square** channels automatically. Users can't :ref:`archive <collaborate/archive-unarchive-channels:archive a channel>`, :ref:`unarchive <collaborate/archive-unarchive-channels:unarchive a channel>`, or leave these channels.
+  All users are added to the **Town Square** channel automatically. This means that users can't :ref:`archive <collaborate/archive-unarchive-channels:archive a channel>`, :ref:`unarchive <collaborate/archive-unarchive-channels:unarchive a channel>`, or leave the **Town Square** channel.
 
 .. tab:: Web/Desktop
 

source/configure/experimental-configuration-settings.rst

@@ -1945,11 +1945,11 @@ This setting isn't available in the System Console and can only be set in ``conf
 
 Default channels every user is added to automatically after joining a new team. Only applies to Public channels, but affects all teams on the server.
 
-When not set, every user is added to the ``off-topic`` and ``town-square`` channels by default.
+When not set, every user is added to the ``town-square`` channel by default.
 
 .. note::
 
-   Even if ``town-square`` and ``off-topic`` aren't listed, every user is added to these channels automatically when joining a new team.
+  Even if ``town-square`` isn't listed, every user is added to that channels automatically when joining a new team.
 
 +----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | This feature's ``config.json`` setting is ``"ExperimentalDefaultChannels": []`` with string array input consisting of channel names, such as ``["announcement", "developers"]``. |

source/getting-started/enterprise-roll-out-checklist.rst

@@ -232,7 +232,7 @@ Now that you have an environment in place, we recommend working through the foll
  - Recommendation: Start with fewer teams in your early roll out
  - Resource: https://docs.mattermost.com/messaging/organizing-channels.html 
 
-- Determine and create key channels to support your users. Town Square and Off-Topic are automatically created channels available on every team
+- Determine and create key channels to support your users. A default Town Square channel is created automatically and available on every team.
 
  - Recommendation: Add a “Support” channel for your users to escalate questions 
 

source/onboard/guest-accounts.rst

@@ -16,7 +16,7 @@ Guest accounts in Mattermost are a way to collaborate with individuals, such as
 
   - A system admin must :ref:`enable guest access <configure/authentication-configuration-settings:guest access>` before guests can be invited.
   - Mattermost Enterprise and Professional customers can :doc:`control who can invite guests </onboard/advanced-permissions>` in their organization. By default, only system admins can invite guests.
-  - Guest accounts count as a paid user in your Mattermost :doc:`workspace </guides/use-mattermost>`. However, guests aren't automatically added to the default **Town-square** and **Off-topic** channels when they log in. You must :doc:`invite guests </collaborate/invite-people>` to individual teams and channels manually. Deactivating a guest account reduces your licensed seat count.
+  - Guest accounts count as a paid user in your Mattermost :doc:`workspace </guides/use-mattermost>`. However, guests aren't automatically added to the default **Town-square** channel when they log in. You must :doc:`invite guests </collaborate/invite-people>` to individual teams and channels manually. Deactivating a guest account reduces your licensed seat count.
   - You'll identify guest users in Mattermost based on their **GUEST** badge next to their name and profile picture. Channels that contain guests also display the message ***This channel has guests** in the channel header.
 
 Guests account limits

source/onboard/user-provisioning-workflows.rst

@@ -13,7 +13,7 @@ User Provisioning
 
 There are currently three recommended user provisioning workflows in Mattermost:
 
-1. **On demand:** If user accounts are not pre-provisioned using one of the methods described below, then a new user account will be provisioned when the user first logs in. When the user logs in, they are asked to select a public team to join (all users must belong to at least one team) and then they are added automatically to Town Square and Off-Topic channels. Mattermost also has a :ref:`default channel setting <configure/experimental-configuration-settings:default channels>` that enables system admins to add everyone to additional channels specified by the organization.
+1. **On demand:** If user accounts are not pre-provisioned using one of the methods described below, then a new user account will be provisioned when the user first logs in. When the user logs in, they are asked to select a public team to join (all users must belong to at least one team) and then they are added automatically to the Town Square channel. Mattermost also has a :ref:`default channel setting <configure/experimental-configuration-settings:default channels>` that enables system admins to add everyone to additional channels specified by the organization.
 2. **Pre-provisioned via bulk import:** Mattermost features a :doc:`bulk data loading tool </onboard/bulk-loading-data>` that can be used for pre-provisioning new users by adding them to teams and channels before their first login to Mattermost. This tool automates the creation of Teams, Channels, Users, and Posts (with file attachments). It can also be used to migrate users and content from an existing system.
 3. **Mattermost API:** The Mattermost `RESTful API <https://api.mattermost.com>`__ can be used to pre-provision new user accounts as well as add and remove them from teams and channels. This model is commonly used by enterprises that have central account provisioning applications.