Update xml/System/GCMemoryInfo.xml

Co-authored-by: Genevieve Warren <[email protected]>

Author: mrsharm

xml/System/GCMemoryInfo.xml

@@ -316,7 +316,7 @@ The memory after `OBJ_D` is not considered part of the `FragmentedBytes` but is
         <summary>Gets the physical memory load when the last garbage collection occurred.</summary>
         <value>The physical memory load, in bytes, when the last garbage collection occurred.</value>
         <remarks>
-          <para>On Windows, memory load is a field in the [MEMORYSTATUS structure](https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-memorystatus) in bytes that denotes the physical memory that's in use if the process isn't running in a container with a memory limit. Otherwise, it's either the cgroup's physical memory in use or the current process' working set if we are on Windows or somehow can't obtain it from Linux. Corresponding information is given on other operating systems.</para>
+          <para>On Windows, memory load is a field in the [MEMORYSTATUS structure](https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-memorystatus) in bytes that denotes the physical memory that's in use if the process isn't running in a container with a memory limit. For other operating systems, or if the process is running on Windows in a container with a memory limit, memory load is either the cgroup's physical memory in use or the current process's working set.</para>
           <para>Data is only brought into physical memory on first touch. If you allocated a big object but haven't actually used it, most of its memory isn't in physical memory. In this case, the allocation won't affect the memory load significantly.</para>
         </remarks>
       </Docs>