Update 3_openbmc_simulate.md

Author: pareenaverma

content/learning-paths/servers-and-cloud-computing/openbmc-rdv3/3_openbmc_simulate.md

@@ -1,5 +1,5 @@
 ---
-title: Run Pre-Silicon OpenBMC and Host UEFI Simulation
+title: Run OpenBMC and Host UEFI Simulation on RD-V3 FVP
 weight: 4
 
 ### FIXED, DO NOT MODIFY
@@ -11,39 +11,39 @@ layout: learningpathall
 With your environment prepared, you can now simulate the full pre-silicon firmware boot flow using the Arm Neoverse RD-V3 reference design.
 You’ll build the OpenBMC image, launch the Arm Fixed Virtual Platform (FVP), and observe the full boot process of both the BMC and host UEFI firmware in a simulated environment.
 
-This simulation launches multiple UART consoles—each mapped to a separate terminal window for different subsystems (e.g., Neoverse V3, Cortex‑M55, Cortex‑M7, and the Cortex-A BMC).
+This simulation launches multiple UART consoles,each mapped to a separate terminal window for different subsystems (e.g., Neoverse V3, Cortex‑M55, Cortex‑M7, and the Cortex-A BMC).
 
-These graphical terminal windows require a desktop session. If you're accessing the simulation over SSH (e.g., on an AWS instance), they may not display properly.
+These graphical terminal windows require a desktop session. If you're accessing the simulation over SSH (e.g., on a cloud instance), they may not display properly.
 
-To ensure proper display and interactivity, we recommend installing a Remote Desktop environment using XRDP.
+To ensure proper display and interactivity, it is recommended to install a Remote Desktop environment using XRDP.
 
-In AWS Ubuntu 22.04 instance, you need install required packages:
+On an Arm cloud Ubuntu 22.04 instance, you will need to install required packages:
 
 ```bash
 sudo apt update
 sudo apt install -y ubuntu-desktop xrdp xfce4 xfce4-goodies pv xterm sshpass socat retry
 sudo systemctl enable --now xrdp
 ```
 
-You may need to follow the Step 2 on RDv3 [learning path](https://learn.arm.com/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/4_rdv3_on_fvp/) to setup the networking and GDM configuration.
+You may need to follow the Step 2 on the [RD-V3 learning path](/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/4_rdv3_on_fvp/) to setup the networking and GDM configuration.
 
 Once connected via Remote Desktop, open a terminal and launch the RD‑V3 FVP simulation:
 
 ## Execute Pre-Silicon OpenBMC Simulation
 
-To make the simulation process smoother and more intuitive, you’ll need to modify a script from Arm’s GitLab repository.
+To make the simulation process more intuitive, you’ll need to modify a script from Arm’s GitLab repository:
 
 ```bash
 cd ~
 wget https://gitlab.arm.com/server_management/PoCs/fvp-poc/-/raw/2a79ae93560969a3b802dfb3d7d89f9fd9dee5a6/run.sh
 ```
 
-Before running the simulation, open the run.sh script and locate the line that defines FVP_KEYWORD.
+Before running the simulation, open the `run.sh` script and locate the line that defines FVP_KEYWORD.
 This variable determines when the host FVP should be launched by monitoring OpenBMC’s console output.
 If not set correctly, the script may hang or fail to start the host simulation.
 Update the line to:
 
-```
+```output
 FVP_KEYWORD="terminal2: Listening for serial connection on port"
 ```
 
@@ -65,7 +65,7 @@ The `run.sh` script will:
 
 Once the simulation is running, the `OpenBMC FVP console` will stop at the Linux login prompt:
 
-```
+```output
 [  OK  ] Started phosphor systemd target monitor.
 [  OK  ] Started Sensor Monitor.
          Starting Hostname Service...
@@ -81,14 +81,14 @@ Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) nodistro.0 fvp ttyA
 fvp login:
 ```
 
-Type OpenBMC default username `root` and password is `0penBmc`.
+Enter the OpenBMC default username `root` and password, which is `0penBmc`.
 
 
 {{% notice Note %}}
 The first character of the password is the number ***0***, not a capital ***O***.
 {{% /notice %}}
 
-After login, you’ll be dropped into the OpenBMC shell — a minimal Linux environment running inside the simulated BMC.
+After login, you will be dropped into the OpenBMC shell, a minimal Linux environment running inside the simulated BMC.
 
 The host-side UEFI simulation will appear in the `FVP terminal_ns_uart0` console. 
 You may briefly see the UEFI Firmware Setup Menu—select `Continue` to proceed with boot. 
@@ -102,8 +102,7 @@ A successful simulation will show login prompts on both BMC and host consoles. Y
 
 ![img2 alt-text#center](openbmc_cssv3_sim.jpg "Simuation Success")
 
-To avoid excessive network bandwidth usage, the following is a 60×-speed simulation recording.
-It gives you a quick visual overview of how OpenBMC and UEFI boot and interact during pre-silicon execution.
+Shown here is a simulation recording. It gives you a quick visual overview of how OpenBMC and UEFI boot and interact during pre-silicon execution.
 
 ![img1 alt-text#center](openbmc_cssv3_running.gif "Simuation Running")
 
@@ -116,5 +115,5 @@ After simulation completes, logs for both the BMC and host will be stored in `~/
 By reviewing the contents of the logs folder, you can verify the expected system behavior or quickly diagnose
 any anomalies that arise during boot or runtime.
 
-With the simulation running successfully, you’re now ready to perform real-time testing between the host and the BMC.  
-In the next module, you’ll explore how to interact with the BMC using UART and IPMI from the host side—validating communication channels in a pre-silicon context.
+With the simulation running successfully, you are now ready to perform real-time testing between the host and the BMC.  
+In the next section, you will explore how to interact with the BMC using UART and IPMI from the host side, validating communication channels in a pre-silicon context.