Address copilot comments

Author: larkox

source/deployment-guide/mobile/mobile-troubleshooting.rst

@@ -143,13 +143,13 @@ If you did not receive a push notification when testing push notifications, use
   - If the log message displays, it means a message was sent to the HPNS server and was not received by your mobile app. Please `create a support ticket <https://support.mattermost.com/hc/en-us/requests/new>`_ with the subject "HPNS issue" for help from Mattermost's Support team.
   - If the log message does not display, it means no mobile push notification was sent to “Account A”. Please repeat the process starting at step 2 and double-check each step.
 
+If push notifications are not being delivered on the mobile device, confirm that you're logged in to the **Native** mobile app session through **Profile > Security > View and Log Out of Active Sessions**. Otherwise, the `DeviceId` won't get registered in the `Sessions` table and notifications won't be delivered.
+
 .. important::
 
   To conserve disk space, once your push notification issue is resolved, go to  **System Console > Environment > Logging > File Log Level**, then select **ERROR** to switch your logging detail level from **DEBUG** to **Errors Only**.
 
 Integration posts (MM Blocks) do not render or respond
 ----------------------------------------------------
 
-If buttons, menus, or structured layout content from an integration post is missing or unresponsive on mobile, see :doc:`Troubleshoot MM Blocks </get-help/mm-blocks-troubleshooting>`.
-
-If push notifications are not being delivered on the mobile device, confirm that you're logged in to the **Native** mobile app session through **Profile > Security > View and Log Out of Active Sessions**. Otherwise, the `DeviceId` won't get registered in the `Sessions` table and notifications won't be delivered.
+If buttons, menus, or structured layout content from an integration post is missing or unresponsive on mobile, see :doc:`Troubleshoot MM Blocks </get-help/mm-blocks-troubleshooting>`.

source/end-user-guide/access/client-availability.rst

@@ -160,7 +160,7 @@ Integrations
 | `Right-hand sidebar <https://developers.mattermost.com/integrate/reference/server/server-reference/>`_          | |checkmark| | |checkmark| |                 |
 +-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+
 
-.. [1] Requires the ``MmBlocksEnabled`` feature flag on the Mattermost server. When disabled, clients do not render native ``mm_blocks`` payloads and the server rejects MM Blocks action requests. Self-hosted deployments can set ``MM_FEATUREFLAGS_MMBLOCKSENABLED=false`` to turn the feature off. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.
+.. [1] Requires ``MM_FEATUREFLAGS_MMBLOCKSENABLED`` to be enabled on the Mattermost server (defaults to ``true``). When set to ``false``, clients do not render native ``mm_blocks`` payloads and the server rejects MM Blocks action requests. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.
 
 Authentication
 ~~~~~~~~~~~~~~

source/get-help/mm-blocks-troubleshooting.rst

@@ -15,7 +15,7 @@ MM Blocks content does not appear
 
 1. **Update your client.** MM Blocks require a current Mattermost web, desktop, or mobile app. See :doc:`client availability </end-user-guide/access/client-availability>` for platform support.
 2. **Confirm the integration payload.** The post must include a non-empty ``props.mm_blocks`` array (or a legacy format such as message attachments that the client translates). Ask your integration owner or system admin to verify the webhook or bot payload.
-3. **Check the feature flag (system admins).** Self-hosted deployments can disable MM Blocks with the ``MmBlocksEnabled`` feature flag. When disabled, native MM Blocks payloads are not rendered and their actions are rejected. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.
+3. **Check the feature flag (system admins).** Self-hosted deployments can disable MM Blocks by setting ``MM_FEATUREFLAGS_MMBLOCKSENABLED=false``. When disabled, native MM Blocks payloads are not rendered and their actions are rejected. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.
 4. **Reload the channel.** Pull to refresh on mobile, or switch channels and return, to fetch the latest post data.
 
 Buttons or menus do not respond

source/integrations-guide/mm-blocks.rst

@@ -20,7 +20,7 @@ Interactive posts combine:
 
 When a post is created, the server encrypts ``props.mm_blocks_actions`` into a single cookie string before the post is sent to clients. Users interact with buttons and menus in the channel; Mattermost calls your integration and can update the post or return an ephemeral reply.
 
-MM Blocks are supported on web, desktop, and mobile clients. Availability is controlled by the ``MmBlocksEnabled`` `feature flag <https://developers.mattermost.com/contribute/more-info/server/feature-flags/>`_, which defaults to ``true``. Self-hosted deployments can set ``MM_FEATUREFLAGS_MMBLOCKSENABLED=false`` to disable rendering and action dispatch for MM Blocks payloads.
+MM Blocks are supported on web, desktop, and mobile clients. Availability is controlled by the ``MM_FEATUREFLAGS_MMBLOCKSENABLED`` `feature flag <https://developers.mattermost.com/contribute/more-info/server/feature-flags/>`_ (defaults to ``true``). Set ``MM_FEATUREFLAGS_MMBLOCKSENABLED=false`` on self-hosted deployments to disable rendering and action dispatch for MM Blocks payloads.
 
 Quick start
 -----------
@@ -73,7 +73,7 @@ Post properties
    * - ``props.mm_blocks_actions``
      - Object keyed by ``action_id``. Each value defines how Mattermost handles a button press or menu selection. Replaced on the wire by an encrypted cookie after the post is saved.
 
-You can include ``props.mm_blocks`` and ``props.mm_blocks_actions`` in any payload that supports a ``props`` object, including :doc:`incoming webhooks </integrations-guide/incoming-webhooks>`, :doc:`outgoing webhook </integrations-guide/outgoing-webhooks>` responses, slash command responses, bot posts, and ephemeral posts created through the API.
+You can include ``props.mm_blocks`` and ``props.mm_blocks_actions`` in any payload that supports a ``props`` object, including :doc:`incoming webhooks </integrations-guide/incoming-webhooks>`, :doc:`outgoing webhooks </integrations-guide/outgoing-webhooks>` responses, slash command responses, bot posts, and ephemeral posts created through the API.
 
 Block types
 -----------