Merge branch 'Roblox:main' into Minor-Changes

content/en-us/chat/legacy/client-side-chat-modules.md

@@ -6,7 +6,7 @@ comments: |
 ---
 
 <Alert severity="error">
-  This guide covers client-side chat modules of the legacy chat system, which is deprecated and no longer onboarding new users in favor of `Class.TextChatService` with easier and more modern chat settings. If you are using the default chat system powered by `Class.TextChatService`, see <a href="../../chat/customizing-in-experience-text-chat.md">In-Experience Text Chat</a>.
+  This guide covers client-side chat modules of the legacy chat system, which is deprecated and no longer onboarding new users in favor of `Class.TextChatService` with easier and more modern chat settings. If you are using the default chat system powered by `Class.TextChatService`, see <a href="../../chat/in-experience-text-chat.md">In-Experience Text Chat</a>.
 </Alert>
 
 You can use the following chat modules to support client-side behaviors of the [Legacy Chat System](../../chat/legacy/legacy-chat-system.md#message-creator-modules).

content/en-us/chat/legacy/server-side-chat-modules.md

@@ -6,7 +6,7 @@ comments: |
 ---
 
 <Alert severity="error">
-  This guide covers server-side chat modules of the legacy chat system, which is deprecated and no longer onboarding new users in favor of `Class.TextChatService` with easier and more modern chat settings. If you are using the default chat system powered by `Class.TextChatService` , see <a href="../../chat/customizing-in-experience-text-chat.md">In-Experience Text Chat</a>.
+  This guide covers server-side chat modules of the legacy chat system, which is deprecated and no longer onboarding new users in favor of `Class.TextChatService` with easier and more modern chat settings. If you are using the default chat system powered by `Class.TextChatService` , see <a href="../../chat/in-experience-text-chat.md">In-Experience Text Chat</a>.
 </Alert>
 
 You can use the following chat modules to support server-side behaviors of the [Legacy Chat System](../../chat/legacy/legacy-chat-system.md#message-creator-modules) including:

content/en-us/production/analytics/performance.md

@@ -120,17 +120,21 @@ The server CPU and memory charts default to the **Overall** view, but have dropd
 
 If a category is higher than usual or appears to be taking up a disproportionate amount of time, use the dropdown menu to drill down on the group and identify processes that could be causing issues.
 
-<img src="../../assets/analytics/performance/perf-dash-drilldown.png" alt="The server CPU time chart showing the physics dropdown." width="600px" />
+<img src="../../assets/analytics/performance/perf-dash-drilldown.png" alt="The server CPU time chart showing the physics dropdown." width="700px" />
 
 <Alert severity="success">
 To exclude a group or process from a chart, click its label in the legend.
 </Alert>
 
-The categories in the dropdown menu map to the ones in the [MicroProfiler](../../studio/microprofiler/index.md), so you can open the MicroProfiler, select **Detailed** or **Timers** modes, and then use the **Groups** menu to filter by the problematic process group.
+- CPU categories and tasks map to the ones in the [MicroProfiler](../../studio/microprofiler/index.md), so you can take [server dumps](../../studio/microprofiler/index.md#profiling-the-server), select **Timers** mode, and then use the **Groups** menu to filter by the problematic process group.
 
-For example, if you spot a potential problem with the **assemble** process under the **Physics** group, you can find it under the same name in the MicroProfiler:
+  For example, if you spot a potential problem with the **assemble** process under the **Physics** group, you can find it under the same name in the MicroProfiler:
 
-<img src="../../assets/analytics/performance/perf-dash-micro.png" alt="The MicroProfiler showing the assemble process within the Physics group." width="500px" />
+  <img src="../../assets/analytics/performance/perf-dash-micro.png" alt="The MicroProfiler showing the assemble process within the Physics group." width="700px" />
+
+- Memory tags map to the ones in `Enum.DeveloperMemoryTag`, with the notable exception of **CoreMemory:Total**, which is equivalent to `Enum.DeveloperMemoryTag.Internal`. You can use the [Developer Console](../../studio/optimization/memory-usage.md#memory) to check tags for excessive usage. This image shows how you might use the Developer Console to investigate an issue with **PlaceMemory:GraphicsTexture** that you see in the dashboard:
+
+  <img src="../../assets/analytics/performance/perf-dash-dev.png" alt="The Developer Console showing the server memory view." width="750px" />
 
 ## Troubleshooting
 

content/en-us/production/publishing/console-guidelines.md

@@ -25,7 +25,7 @@ Apply the following to simplify the UI design for consoles:
 
 - **Minimal controller input complexity**: Unlike tappable or clickable input methods, console users navigate by pressing one button at a time, so an action that takes one move on other devices might take extra moves with a controller. Make sure that key actions in your experience only take a few moves to access.
 
-- **No Chat Window**: Regardless of whether you use the default in-experience text chat system or fork the legacy chat system as your custom chat system, [disable the chat window](../../chat/customizing-in-experience-text-chat.md#chat-window-configuration) for console experiences.
+- **No Chat Window**: Regardless of whether you use the default in-experience text chat system or fork the legacy chat system as your custom chat system, [disable the chat window](../../chat/chat-window.md#chat-window-configuration) for console experiences.
 
 <Alert severity="info">
 As controllers aren't just for consoles and VR but also are available on devices such as desktop and mobile, minimizing the number of moves needed can enhance the UI for all devices and input types in addition to PlayStation and Xbox.