Update kernel build docs

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/kernel-build/_next-steps.md

@@ -4,26 +4,7 @@ next_step_guidance: >
     
 recommended_path: "/learning-paths/servers-and-cloud-computing/profiling-for-neoverse/"
 
-further_reading:
-    - resource:
-        title: TuxMake documentation
-        link: https://tuxmake.org/
-        type: documentation
-    - resource:
-        title: Linux kernel documentation
-        link: https://www.kernel.org/doc/html/latest/
-        type: documentation
-    - resource:
-        title: arm_kernel_install_guide repository
-        link: https://github.com/geremyCohen/arm_kernel_install_guide
-        type: website
-    - resource:
-        title: Arm Neoverse system architecture
-        link: https://developer.arm.com/documentation/den0024/latest/
-        type: documentation
-
-
-### FIXED, DO NOT MODIFY THIS FILE, unless you need to update the 'further_reading' list.
+### FIXED, DO NOT MODIFY THIS FILE.
 weight: 21
 layout: learningpathall
 ---

content/learning-paths/servers-and-cloud-computing/kernel-build/how-to-3.md

@@ -13,9 +13,9 @@ Fastpath builds use the same TuxMake pipelines but add a configuration fragment
 Fastpath workflows are build-only: don't combine `--fastpath true` (or the demo shortcut) with `--kernel-install` or any `--install-from` commands. 
 
 The proper workflow is:
-1. Build the kernel with Fastpath configuration enabled
-2. Copy the flat artifacts (`Image.gz`, `modules.tar.xz`, and `config`) to the Fastpath host
-3. Let the Fastpath tooling handle deployment to the SUT (System Under Test)
+- Build the kernel with Fastpath configuration enabled
+- Copy the flat artifacts (`Image.gz`, `modules.tar.xz`, and `config`) to the Fastpath host
+- Let the Fastpath tooling handle deployment to the SUT (System Under Test)
 
 ### Install Docker for Fastpath