avoiding several sentences starting with you'll consecutively

Author: anupras-mohapatra-arm

content/learning-paths/automotive/openadkit1_container/_index.md

@@ -31,7 +31,7 @@ generated_summary_faq:
   faq_source_hash: 37913b2c4aed914d32dbdad054ebdd2b1d4587da3ede1a33ba81e3e68bf504a3
   summary: >-
     You'll deploy a containerized Autoware
-    Open AD Kit simulation on Arm Neoverse using Docker and Docker Compose, within a SOAFEE-aligned Shift-Left workflow. You'll first learn about software-defined vehicles (SDVs), SOAFEE, ROS 2, and the Open AD Kit components used in the demo. You'll then prepare an Arm Neoverse Linux system and use Docker Compose to start the Open AD Kit visualizer, planning, and simulation services. By the end, you'll review a running simulation. The workflow has been tested on both cloud (Amazon EC2) and on-premise Arm Neoverse platforms.
+    Open AD Kit simulation on Arm Neoverse using Docker and Docker Compose, within a SOAFEE-aligned Shift-Left workflow. First, you'll learn about software-defined vehicles (SDVs), SOAFEE, ROS 2, and the Open AD Kit components used in the demo. Then, you'll prepare an Arm Neoverse Linux system and use Docker Compose to start the Open AD Kit visualizer, planning, and simulation services. By the end, you'll review a running simulation. The workflow has been tested on both cloud (Amazon EC2) and on-premise Arm Neoverse platforms.
   faqs:
   - question: What result should I expect after launching the Docker Compose stack?
     answer: >-

content/learning-paths/automotive/openadkit2_safetyisolation/_index.md

@@ -33,8 +33,8 @@ generated_summary_faq:
   summary: >-
     You'll learn about prototyping safety‑critical isolation for autonomous
     driving workloads on Arm Neoverse by applying functional safety concepts, ISO 26262 and ASIL
-    guidance, and a safety‑island architecture. You'll understand how to separate safety‑critical control
-    logic from non‑safety functions, then connect components using a publish‑subscribe model (DDS/ROS
+    guidance, and a safety‑island architecture. First, you'll understand how to separate safety‑critical control
+    logic from non‑safety functions. Then, you'll connect components using a publish‑subscribe model (DDS/ROS
     2) within containerized deployments or across Arm‑based instances. You'll explore lifecycle
     practices aligned with the V‑model, including clear requirements, version control, impact
     analysis, and regression testing. By the end, you'll organize simulation components into

content/learning-paths/automotive/system76-auto/_index.md

@@ -30,8 +30,8 @@ generated_summary_faq:
   faq_source_hash: 2b758d2dcf28a683ab164e28578a736d6d730b81dfbc01a6765619052fcdebd0
   summary: >-
     You'll use a System76 Thelio Astra Arm desktop to build and run the
-    Arm Automotive Solutions Software Reference Stack in a local Multipass virtual machine. You'll
-    create an Ubuntu 20.04 guest, isolate builds, and compile Yocto-based
+    Arm Automotive Solutions Software Reference Stack in a local Multipass virtual machine. You'll start by 
+    creating an Ubuntu 20.04 guest, isolating builds, and compiling Yocto-based
     components targeting a Fixed Virtual Platform that models the Arm Reference Design-1 AE. You'll review the Thelio Astra platform and the software stack context, then run a Parsec-enabled TLS demo that establishes an HTTPS session to transfer a web page.
   faqs:
   - question: Which Multipass install guide should I follow before creating the virtual machine?

content/learning-paths/automotive/zenacssdebug/_index.md

@@ -34,7 +34,7 @@ generated_summary_faq:
   faq_source_hash: 74740788edbfe7ea09bf955455b4aeaed00e667fa8c9d68467353c1f64528b08
   summary: >-
     You'll debug the Arm Zena Compute Subsystem (CSS) reference
-    software stack on a Fixed Virtual Platform using Arm Development Studio. You'll launch the
+    software stack on a Fixed Virtual Platform using Arm Development Studio. First, you'll launch the
     FVP with the Iris debug server enabled, then create and save a custom Arm DS configuration. You'll establish connections
     to each heterogeneous component within Zena CSS to debug the Linux kernel and user processes. By the end, you'll create reusable `.launch`
     files, step through early RSE boot, and attach to Safety Island and Linux targets to inspect

content/learning-paths/servers-and-cloud-computing/rafay-eks/_index.md

@@ -36,7 +36,7 @@ generated_summary_faq:
   summary: >-
     You'll provision an Amazon EKS cluster on Arm using
     the Rafay Kubernetes Operations Platform and validate workloads on AWS Graviton-based nodes.
-    You'll define a declarative cluster manifest in Rafay referencing an existing project,
+    First, you'll define a declarative cluster manifest in Rafay referencing an existing project,
     blueprint, and cloud credential. Then, you'll create the EKS cluster and deploy NGINX pinned to arm64 
     to confirm scheduling on Graviton-based instances. Finally, you'll remove the NGINX workload and deprovision the EKS resources to avoid ongoing cloud costs.
   faqs: