Content review

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/arm_linux_page_size/centos.md

@@ -5,11 +5,11 @@ weight: 5
 layout: learningpathall
 ---
 
-Follow the steps below to install a 64K page size kernel on [CentOS 9  or newer](https://www.centos.org/download/).
+Follow the steps below to install a 64K page size kernel on [CentOS 9  or later](https://www.centos.org/download/).
 
 ## Verify the current page size
 
-Verify you’re using a 4 KB pagesize kernel by entering the following commands:
+Verify you’re using a 4KB pagesize kernel by entering the following commands:
 
 ```bash
 getconf PAGESIZE
@@ -25,9 +25,9 @@ The output should be similar to below. The kernel flavor (the string after the v
 
 The 4096 indicates the current page size is 4KB. If you see a value that is different, you are already using a page size other than 4096 (4K).  On Arm systems, the valid options are 4K, 16K, and 64K.
 
-## Install the 64k kernel package:
+## Install the 64K kernel package:
 
-Enter the command below to install the 64k kernel:
+Enter the command below to install the 64K kernel:
 
 ```bash
 sudo dnf -y install kernel-64k
@@ -68,7 +68,7 @@ The output shows the 64k kernel is running:
 5.14.0-583.el9.aarch64+64k
 ```
 
-## Revert back to the 4K kernel
+## Revert to the 4K kernel
 
 To revert to the original 4K kernel, enter the following:
 
@@ -100,7 +100,7 @@ sudo grubby --set-default "$k4"
 sudo reboot
 ```
 
-Upon reboot, verify you’re on a 4 KB pagesize kernel by entering the following commands:
+Upon reboot, verify you’re on a 4KB pagesize kernel by entering the following commands:
 
 ```bash
 getconf PAGESIZE

content/learning-paths/servers-and-cloud-computing/arm_linux_page_size/debian.md

@@ -5,7 +5,7 @@ weight: 4
 layout: learningpathall
 ---
 
-Follow the steps below to install a 64K page size kernel on [Debian 11 “Bullseye” or newer](https://www.debian.org/releases/bullseye/).
+Follow the steps below to install a 64K page size kernel on [Debian 11 “Bullseye” or later](https://www.debian.org/releases/bullseye/).
 
 Debian does not provide a 64K kernel package, so you will need to compile it from source.  
 
@@ -17,7 +17,7 @@ The instructions below use the Debian source package.
 
 ## Verify the current page size
 
-Verify you’re using a 4 KB pagesize kernel by entering the following commands:
+Verify you’re using a 4KB pagesize kernel by entering the following commands:
 
 ```bash
 getconf PAGESIZE
@@ -100,11 +100,11 @@ The output shows the 64k kernel is running:
 6.12.22-64k
 ```
 
-This indicates the current page size is 64K, and you are using the new custom made 64k kernel.  
+This indicates the current page size is 64K, and you are using the new custom-built 64k kernel.  
 
-## Revert back to the 4K kernel
+## Revert to the 4K kernel
 
-To revert back to the kernel we started with, enter:
+To revert to the kernel we started with, enter:
 
 ```bash
 dpkg-query -W -f='${Package}\n' 'linux-image-*-64k*' 'linux-headers-*-64k*' \
@@ -127,4 +127,4 @@ The output should be similar to below -- the full kernel name may vary, but the
 6.1.0-34-cloud-arm64
 ```
 
-The 4096 indicates the current page size has been reverted to 4KB. 
+The 4096 indicates the current page size has been reverted to 4 KB. 

content/learning-paths/servers-and-cloud-computing/arm_linux_page_size/overview.md

@@ -1,19 +1,19 @@
 ---
-title: Why does page size matter?
+title: Overview
 weight: 2
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
 
-## Background
+## Page size fundamentals
 
-Before you modify the Linux kernel page size on an Arm system, you need to know what a page is, why page size matters, and how page size directly affects performance.
+Before you modify the Linux kernel page size on an Arm system, you need to know what a page is, why size matters, and how size affects performance.
 
 ## What’s a memory page?
 
 Think of your computer’s memory like a big sheet of graph paper. Each page is one square on that sheet. 
 
-The page table is the legend that identifies which square, the *virtual address*, maps to which corresponding spot in physical RAM. Each page represents a fixed-size block of virtual memory that maps to physical memory through the page table. This mapping is managed by the operating system and the CPU’s Memory Management Unit (MMU).
+The page table acts like a legend on the map, showing which virtual address square corresponds to a specific location in physical RAM. This mapping is managed by the operating system and the CPU’s Memory Management Unit (MMU).
 
 To keep track of these mappings efficiently, CPUs use a fast lookup cache called the Translation Lookaside Buffer (TLB). Every access first attempts a TLB hit; a miss forces a page table lookup. If the page isn't already in the TLB, the CPU must fetch the mapping from memory—a process that adds latency and stalls execution.
 
@@ -66,7 +66,7 @@ In addition, the page size might need to be reviewed over time as the applicatio
 The best way to determine the impact of page size on application performance is to experiment with both options.
 
 {{% notice Warning%}}
-Do not test in a production environment - modifying the Linux kernel page size can lead to system instability or failure. Perform testing in a non-production environment before applying to production systems.
+Do not modify the Linux kernel page size in a production environment. It can lead to system instability or failure. Perform testing in a non-production environment before applying to production systems.
 {{% /notice %}}
 
 Select the Arm Linux distribution you are using to find out how to install the 64K page size kernel.

content/learning-paths/servers-and-cloud-computing/arm_linux_page_size/ubuntu.md

@@ -5,11 +5,11 @@ weight: 3
 layout: learningpathall
 ---
 
-Follow the steps below to install a 64K page size kernel on [Ubuntu 22.04 LTS or newer](https://releases.ubuntu.com/22.04/).
+To install a 64 K page size kernel on [Ubuntu 22.04 LTS or later](https://releases.ubuntu.com/22.04/), follow the steps below.
 
 ## Verify the current page size
 
-Verify you’re using a 4 KB pagesize kernel by entering the following commands:
+Verify you’re using a 4KB base-page-size kernel by entering the following commands:
 
 ```bash
 getconf PAGESIZE
@@ -23,7 +23,7 @@ The output should be similar to below. The kernel flavor (the string after the v
 6.1.0-34-cloud-arm64
 ```
 
-The 4096 indicates the current page size is 4KB. If you see a value that is different, you are already using a page size other than 4096 (4K).  On Arm systems, the valid options are 4K, 16K, and 64K.
+The 4096 indicates the current page size is 4 KB. If you see a value that is different, you are already using a page size other than 4096 (4K).  On Arm systems, the valid options are 4K, 16K, and 64K.
 
 ## Install the required dependencies and the 64K kernel
 
@@ -34,15 +34,15 @@ sudo apt-get -y update
 sudo apt-get -y install git build-essential autoconf automake libtool gdb wget linux-generic-64k
 ```
 
-Next, run the following command to configure grub to load the 64K kernel by default:
+Next, run the following command to configure GRUB to load the 64K kernel by default:
 
 ```bash
 echo "GRUB_FLAVOUR_ORDER=generic-64k" | sudo tee /etc/default/grub.d/local-order.cfg 
 ```
 
-## Update grub and reboot
+## Update GRUB and reboot
 
-Commit your changes to grub and reboot by entering the following:
+Commit your changes to GRUB and reboot by entering the following:
 
 ```bash
 sudo update-grub 
@@ -56,32 +56,32 @@ getconf PAGESIZE
 uname -r
 ```
 
-The output shows the 64k kernel is running: 
+The output shows the 64K kernel is running: 
 
 ```output
 65536
 6.8.0-59-generic-64k
 ```
 
-This indicates the current page size is 64K and you are running the new 64K kernel.  
+This indicates that the current page size is 64K and that you are running the new 64K kernel.  
 
-## Revert back to the 4K kernel
+## Revert to the 4K kernel
 
-To revert back to the original 4K kernel, run the following commands:
+To revert to the original 4K kernel, run the following commands:
 
 ```bash
 echo "GRUB_FLAVOUR_ORDER=generic" | sudo tee /etc/default/grub.d/local-order.cfg 
 sudo update-grub 
 sudo reboot 
 ```
-Upon reboot, verify you’re on a 4 KB pagesize kernel by entering the following commands:
+Upon reboot, verify you’re on a 4KB pagesize kernel by entering the following commands:
 
 ```bash
 getconf PAGESIZE
 uname -r
 ```
 
-The output shows the 4k kernel is running: 
+The output shows the 4K kernel is running: 
 
 ```output
 4096