trimming

Author: anupras-mohapatra-arm

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

@@ -1,5 +1,5 @@
 ---
-title: Learn how to optimize an application with BOLT
+title: Optimize an application with BOLT
 description: Learn how to build, profile, and optimize Arm executables using BOLT post-link binary optimization to improve application performance through code layout improvements.
 
 minutes_to_complete: 30
@@ -33,8 +33,7 @@ generated_summary_faq:
     You'll use BOLT to post-link optimize an Arm Linux executable
     based on real execution profiles. First, you'll prepare a target system for profiling and optionally
     a separate build/BOLT system, then choose a profiling method — Perf samples, ETM, or SPE — to
-    collect runtime behavior into a `perf.data` file. You'll convert the profile for BOLT, and run BOLT to reorder code layout and emit a new optimized executable. By the end, you'll make an informed choice about how to collect profiles, produce the expected artifacts,
-    and run the optimization steps in sequence to compare the resulting binary against
+    collect runtime behavior into a `perf.data` file. You'll convert the profile for BOLT, and run BOLT to reorder code layout and emit a new optimized executable. Finally, you'll compare the resulting binary against
     the original to observe improvements.
   faqs:
   - question: How should I choose between Perf samples, ETM, and SPE for profiling?

content/learning-paths/servers-and-cloud-computing/cca-kata/_index.md

@@ -35,7 +35,7 @@ generated_summary_faq:
     First, you'll learn about the Confidential Containers design, understand which components run inside the
     Trusted Execution Environment, and see how Trustee services use Arm CCA
     attestation to authorize decryption. Then, you'll start the Trustee services and a local Docker
-    registry, publish an encrypted image, and launch the container on the FVP. By the end, you'll complete an end-to-end confidential execution workflow and confirm attestation, key release, and that the workload runs in a Realm only
+    registry, publish an encrypted image, and launch the container on the FVP. By the end, you'll confirm attestation, key release, and that the workload runs in a Realm only
     after authorization.
   faqs:
   - question: How do I know the Trustee services are ready before pushing the image?

content/learning-paths/servers-and-cloud-computing/circleci-gcp/_index.md

@@ -40,9 +40,8 @@ generated_summary_faq:
     You'll provision a SUSE Linux Google Cloud C4A virtual machine (VM) powered by Google Axion,
     install the CircleCI CLI, create a custom resource class, and deploy the CircleCI Machine
     Runner so CI/CD jobs execute natively on Arm. After configuring a self-hosted runner linked
-    to a CircleCI namespace, you'll author a workflow that targets the resource class and runs a
-    small Node.js demo app on the Arm VM. By the end, you'll dispatch a CircleCI job
-    to the Arm runner and verify its execution in the CircleCI dashboard
+    to a CircleCI namespace, you'll author and dispatch a workflow that targets the resource class and runs a
+    small Node.js demo app on the Arm VM. You'll then verify its execution in the CircleCI dashboard
     and on the VM.
   faqs:
   - question: How do I know I created the correct C4A Arm VM in Google Cloud?