edits

Author: anupras-mohapatra-arm

content/learning-paths/mobile-graphics-and-gaming/ams/fa.md

@@ -50,9 +50,9 @@ After connecting to your device, you can capture a frame burst.
 
 2. You can capture one frame burst of up to three consecutive frames. Adjust the **Frame count** as required.
 
-3. Select the **Capture** button to start capturing the frame burst. Wait for the capture to complete. This may take several seconds.
+3. Select the **Capture** button to start capturing the frame burst. Wait for the capture to complete. This might take several seconds.
 
-4. Select **Analyze** to see the results. It may take a few minutes to analyze the data.
+4. Select **Analyze** to see the results. It might take a few minutes to analyze the data.
 
 ## Analyze the capture
 
@@ -72,7 +72,7 @@ Explore each frame to evaluate how efficiently they were rendered on the device.
 
     ![Framebuffers view in Frame Advisor showing the selected draw call output so you can step through how the frame is built#center](images/fa_frame_buffer_view.png)
 
-3. In the **Content Metrics** view, sort draw calls by the number of primitives to find the most expensive objects. See whether these objects could be simplified.
+3. In the **Content Metrics** view, sort draw calls by the number of primitives to find the most expensive objects. See whether these objects can be simplified.
 
     ![Content Metrics view in Frame Advisor sorted by primitive count with the Prims column highlighted to identify expensive draw calls#center](images/fa_content_metrics.png)
 

content/learning-paths/mobile-graphics-and-gaming/ams/malioc.md

@@ -46,7 +46,7 @@ Mali Offline Compiler generates a performance report.
 
 If your frame analysis points to shader cost, compile one of your shaders. You can also use this sample shader to learn how to read the report. 
 
-An example (`OpenGL ES`) shader is provided in [Compile your shader](https://developer.arm.com/documentation/102468/latest/Compile-your-shader) in the Arm documentation:
+The following example (`OpenGL ES`) shader is provided in [Compile your shader](https://developer.arm.com/documentation/102468/latest/Compile-your-shader) in Arm documentation:
 ```C
 #version 310 es
 #define WINDOW_SIZE 5
@@ -100,7 +100,7 @@ Longest path cycles:         4.53    0.00    0.25    2.50        A
 A = Arithmetic, LS = Load/Store, V = Varying, T = Texture
 ```
 
-An example optimization is described in [Optimize your shader](https://developer.arm.com/documentation/102468/latest/Optimize-your-shader) in the Arm documentation:
+An example optimization is described in [Optimize your shader](https://developer.arm.com/documentation/102468/latest/Optimize-your-shader) in Arm documentation:
 
 ```C
 #version 310 es

content/learning-paths/mobile-graphics-and-gaming/ams/pa.md

@@ -93,7 +93,7 @@ For full instructions, see the [Get started with Performance Advisor Tutorial](h
     streamline-cli -pa <options> my_capture.apc
     ```
 
-    For a list of available options, see [The Streamline-cli -pa command](https://developer.arm.com/documentation/102009/9-7/Command-line-options/The-Streamline-cli--pa-command) in the Arm documentation, or run the following command:
+    For a list of available options, see [The Streamline-cli -pa command](https://developer.arm.com/documentation/102009/9-7/Command-line-options/The-Streamline-cli--pa-command) in Arm documentation, or run the following command:
 
     ```console
     streamline-cli -pa -h
@@ -118,10 +118,10 @@ This feature is particularly useful when used within a [CI workflow](https://dev
 
 ## Specify performance budgets
 
-You can specify a performance budget that is reflected in the Performance Advisor report. For more information, see [Setting performance budgets](https://developer.arm.com/documentation/102009/latest/Quick-start-guide/Setting-performance-budgets) in the Arm documentation.
+You can specify a performance budget that is reflected in the Performance Advisor report. For more information, see [Setting performance budgets](https://developer.arm.com/documentation/102009/latest/Quick-start-guide/Setting-performance-budgets) in Arm documentation.
 
 ## What you've accomplished and what's next
 
 You've now generated JSON and HTML Performance Advisor reports for your application.
 
-Next, you'll perform frame-based analysis on your application using Frame Advisor.
+Next, you'll perform frame-based analysis on your application using Frame Advisor.

content/learning-paths/mobile-graphics-and-gaming/ams/renderdoc.md

@@ -12,7 +12,7 @@ layout: "learningpathall"
 
 ## Run RenderDoc for Arm GPUs
 
-[RenderDoc for Arm GPUs](https://developer.arm.com/Tools%20and%20Software/RenderDoc%20for%20Arm%20GPUs) is an Arm fork of the [RenderDoc](https://renderdoc.org/) open-source debugger. 
+[RenderDoc for Arm GPUs](https://developer.arm.com/Tools%20and%20Software/RenderDoc%20for%20Arm%20GPUs) is an Arm fork of the [RenderDoc](https://renderdoc.org/) open-source debugger.
 
 The Arm release includes support for API features and extensions that are available on the latest Arm GPUs, but not yet supported in upstream RenderDoc. Arm intends to contribute changes to the upstream project, but some Arm-specific or Android-specific features might be available only in the Arm fork.
 
@@ -52,7 +52,7 @@ To run RenderDoc for Arm GPUs:
 
     Selected events are highlighted with a green flag. The other windows in the UI update to display information for the selected event, including the render state, data resources, and GPU output.
 
-See the [RenderDoc documentation](https://renderdoc.org/docs/index.html#) to explore the full list of features.
+For a full list of features, see the [RenderDoc documentation](https://renderdoc.org/docs/index.html#).
 
 ## What you've accomplished and what's next
 

content/learning-paths/mobile-graphics-and-gaming/ams/streamline.md

@@ -49,7 +49,7 @@ The charts in the **Timeline** view show the performance counter activity captur
 
 For instructions to use the features in the **Timeline** view, see the [Streamline User Guide](https://developer.arm.com/documentation/101816/latest/Analyze-your-capture).
 
-Understanding the output of Streamline is key to the usefulness of the tool. To understand how to interpret the capture from different points of view, see [Android performance triage with Streamline](https://developer.arm.com/documentation/102540/latest/).
+To understand how to interpret the capture from different points of view, see [Android performance triage with Streamline](https://developer.arm.com/documentation/102540/latest/).
 
 ## What you've accomplished and what's next