summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide/mm
diff options
context:
space:
mode:
authorAmos Wenger <amos@bearcove.net>2023-10-06 13:26:36 +0200
committerJonathan Corbet <corbet@lwn.net>2023-10-10 13:35:55 -0600
commit2087f270bebb78adc5059fd040e2691cd7f9bb5c (patch)
tree255cb8339aee79d29f32ee9be4701a121a93a8bc /Documentation/admin-guide/mm
parent5ccba71f928f4abd87cbea680e27e2cedd3293b0 (diff)
downloadlinux-2087f270bebb78adc5059fd040e2691cd7f9bb5c.tar.gz
linux-2087f270bebb78adc5059fd040e2691cd7f9bb5c.tar.bz2
linux-2087f270bebb78adc5059fd040e2691cd7f9bb5c.zip
mm/memory-hotplug: fix typo in documentation
I'm 90% sure memory hotunplugging doesn't involve a "fist" phase Signed-off-by: Amos Wenger <amos@bearcove.net> Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20231006112636.97128-1-amos@bearcove.net
Diffstat (limited to 'Documentation/admin-guide/mm')
-rw-r--r--Documentation/admin-guide/mm/memory-hotplug.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
index 01595965734a..aa50b8501c2e 100644
--- a/Documentation/admin-guide/mm/memory-hotplug.rst
+++ b/Documentation/admin-guide/mm/memory-hotplug.rst
@@ -75,7 +75,7 @@ Memory hotunplug consists of two phases:
(1) Offlining memory blocks
(2) Removing the memory from Linux
-In the fist phase, memory is "hidden" from the page allocator again, for
+In the first phase, memory is "hidden" from the page allocator again, for
example, by migrating busy memory to other memory locations and removing all
relevant free pages from the page allocator After this phase, the memory is no
longer visible in memory statistics of the system.