refinfra: minor wording update

Minor wording updates to improve readability.
Adds external links for further reading.

Signed-off-by: Daniel Nguyen <[email protected]>

Author: danielnguyen-arm

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/_index.md

@@ -11,9 +11,11 @@ learning_objectives:
     - Test the reference firmware stack.
 
 prerequisites:
-    - Some understanding of the Reference Design software stack architecture.
+    - Some understanding of the [Reference Design software stack architecture](https://neoverse-reference-design.docs.arm.com/en/latest/about/software_stack.html).
+    - Some understanding of the Linux command line.
+    - Optionally a basic understanding of Docker and containers.
 
-author_primary: Tom Pilar
+author_primary: Tom Pilar, Daniel Nguyen
 
 ### Tags
 skilllevels: Introductory

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/build-2.md

@@ -1,5 +1,5 @@
 ---
-title: Build the software stack
+title: Build the Software Stack
 weight: 3
 
 ### FIXED, DO NOT MODIFY
@@ -79,5 +79,5 @@ lrwxrwxrwx 1 ubuntu ubuntu      30 Jan 12 15:35 tf-bl31.bin -> ../components/rdn
 lrwxrwxrwx 1 ubuntu ubuntu      33 Jan 12 15:35 uefi.bin -> ../components/css-common/uefi.bin
 ```
 
-The `fip-uefi.bin` firmware image will contain the `TF-A BL2` boot loader image which is responsible for unpacking the rest of the firmware as well as the firmware that TF-A BL2 unpacks. This includes the `SCP BL2` (`scp_ramfw.bin`) image that is unpacked by the AP firmware and transferred over to the SCP TCMs using the SCP shared data store module. Along with the FIP image, the FVP also needs the `TF-A BL1` image and the `SCP BL1` (`scp_romfw.bin`) image files.
+The `fip-uefi.bin` [firmware image package](https://trustedfirmware-a.readthedocs.io/en/v2.5/getting_started/tools-build.html) will contain the `TF-A BL2` boot loader image which is responsible for unpacking the rest of the firmware as well as the firmware that TF-A BL2 unpacks. This includes the `SCP BL2` (`scp_ramfw.bin`) image that is unpacked by the AP firmware and transferred over to the SCP TCMs using the SCP shared data store module. Along with the FIP image, the FVP also needs the `TF-A BL1` image and the `SCP BL1` (`scp_romfw.bin`) image files.
 

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/environment-setup-1.md

@@ -12,7 +12,7 @@ This learning path is based on the `Neoverse N2` Reference Design (`RD-N2`).
 
 ## Before you begin
 
-You can use either an AArch64 or x86_64 host machine running Ubuntu Linux 22.04. 64GB of free disk space and 32GB of RAM is minimum requirement to sync and build the platform software stack. 48GB of RAM is recommended.
+You can use either an AArch64 or x86_64 host machine running **Ubuntu Linux 22.04**. 64GB of free disk space and 32GB of RAM is minimum requirement to sync and build the platform software stack. 48GB of RAM is recommended.
 
 Follow the instructions to set up your environment using the information found at the [Neoverse RD-N2 documentation site](https://neoverse-reference-design.docs.arm.com/en/latest/platforms/rdn2.html).
 
@@ -53,7 +53,7 @@ Bug reports: https://bugs.chromium.org/p/gerrit/issues/entry?template=Repo+tool+
 
 Create a new directory in to which you can download the source code, build the stack, and then obtain the manifest file.
 
-To obtain the manifest, choose a tag of the platform reference firmware. [RD-INFRA-2023.09.29](https://neoverse-reference-design.docs.arm.com/en/latest/releases/RD-INFRA-2023.09.29/release_note.html) is used here. See the [release notes](https://neoverse-reference-design.docs.arm.com/en/latest/) for more information.
+To obtain the manifest, choose a tag of the platform reference firmware. [RD-INFRA-2023.09.29](https://neoverse-reference-design.docs.arm.com/en/latest/releases/RD-INFRA-2023.09.29/release_note.html) is used here, although it is recommended to use the latest version available. See the [release notes](https://neoverse-reference-design.docs.arm.com/en/latest/) for more information.
 
 Specify the platform you would like with the manifest. In the [manifest repo](https://git.gitlab.arm.com/infra-solutions/reference-design/infra-refdesign-manifests) there are a number of available platforms. In this case, select `pinned-rdn2.xml`.
 

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/test-with-fvp-3.md

@@ -127,7 +127,7 @@ In your original terminal, launch the FVP using the supplied script:
 Observe the platform is running successfully:
 ![fvp terminals alt-text#center](images/uefi.png "Figure 2. FVP Terminals")
 
-To boot into `busy-box`, use:
+You can also boot into `busy-box`, using the command:
 ```bash
 ./boot.sh -p rdn2
 ```