Merge pull request #3032 from pareenaverma/content_review

Performix updated install guide

Author: pareenaverma

content/install-guides/asct.md

@@ -23,7 +23,7 @@ author:
 
 ### PAGE SETUP
 weight: 1                       # Defines page ordering. Must be 1 for first (or only) page.
-tool_install: false             # Set to true to be listed in main selection page, else false
+tool_install: true             # Set to true to be listed in main selection page, else false
 multi_install: false            # Set to true if first page of multi-page article, else false
 multitool_install_part: false   # Set to true if a sub-page of a multi-page article, else false
 layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles

content/install-guides/atp.md content/install-guides/performix.mdcontent/install-guides/atp.md renamed to content/install-guides/performix.md

@@ -17,7 +17,7 @@ You don't need to understand the Mandelbrot algorithm in detail to follow this L
 
 ## Connect to Target
 
-If this is your first time setting up Arm Performix, follow the [Arm Performix installation guide](/install-guides/atp/). In this Learning Path you'll connect to an AWS Graviton3 metal instance (`m7g.metal`) with 64 Neoverse V1 cores, your remote target server. From the host machine, test the connection to the remote server by navigating to **Targets** > **Test Connection**. You should see the successful connection screen below.
+If this is your first time setting up Arm Performix, follow the [Arm Performix installation guide](/install-guides/performix/). In this Learning Path you'll connect to an AWS Graviton3 metal instance (`m7g.metal`) with 64 Neoverse V1 cores, your remote target server. From the host machine, test the connection to the remote server by navigating to **Targets** > **Test Connection**. You should see the successful connection screen below.
 
 ![The Arm Performix Targets panel showing a successful connection test result for a remote Arm server#center](./successful-connection.jpg "Successful connection to remote target")
 
@@ -43,4 +43,4 @@ Build the application:
 make single_thread DEBUG=1
 ```
 
-This creates the binary `./builds/mandelbrot_single_thread_debug`.
+This creates the binary `./builds/mandelbrot_single_thread_debug`.

content/learning-paths/servers-and-cloud-computing/cpu_hotspot_performix/how-to-2.md

@@ -16,7 +16,7 @@ A Mandelbrot set generator is a classic computer science application used to tes
 
 Make sure Arm Performix is installed on your host machine. The host machine is your local computer where the Arm Performix GUI runs, and it can be a Windows, macOS, or Linux machine. The target machine is the Linux server where your application is compiled and where the application runs.
 
-If you don't have Arm Performix installed, see the [Arm Performix install guide](/install-guides/atp/). 
+If you don't have Arm Performix installed, see the [Arm Performix install guide](/install-guides/performix/). 
 
 From the host machine, open the Arm Performix application and navigate to the **Targets** tab. Set up an SSH connection to the target that runs the workload, and test the connection. For the examples in this guide, you connect to an Arm Neoverse-based server.
 
@@ -65,4 +65,4 @@ In this section:
 - You set up the target machine and established an SSH connection.
 - You downloaded, compiled, and ran the baseline Mandelbrot application.
 
-Next, you'll use the CPU Microarchitecture recipe to identify performance bottlenecks in the application.
+Next, you'll use the CPU Microarchitecture recipe to identify performance bottlenecks in the application.

content/learning-paths/servers-and-cloud-computing/performix-microarchitecture/1-setup.md

@@ -30,7 +30,7 @@ int main(int argc, char* argv[]){
 }
 ```
 
-When Arm Performix launches the executable on the target machine, it does so from a temporary agent directory, `/tmp/atperf/tools/atperf-agent`. If your code uses a relative path to save the image, the image is written to that temporary folder and might be deleted or you can't find it. 
+When Arm Performix launches the executable on the target machine, it does so from a temporary agent directory. If your code uses a relative path to save the image, the image is written to that temporary folder and might be deleted or you can't find it. 
 
 To prevent this, edit the `myplot.draw()` line in `main.cpp` to use the absolute path to your project's image folder (for example, `/home/ubuntu/mandelbrot-example/Green-Parallel-512.bmp`), and then rebuild the application.
 
@@ -74,4 +74,4 @@ In this section:
 - You ran the CPU Microarchitecture recipe on the Mandelbrot application.
 - You identified that the application spends most of its time in Backend Stalls without using SIMD operations.
 
-Next, you'll run the Instruction Mix recipe to confirm where optimization opportunities exist and implement vectorization.
+Next, you'll run the Instruction Mix recipe to confirm where optimization opportunities exist and implement vectorization.

content/learning-paths/servers-and-cloud-computing/performix-microarchitecture/2-run-cpu-uarch.md

@@ -1,9 +1,6 @@
 ---
 title: Optimize application performance using Arm Performix CPU microarchitecture analysis
 
-draft: true
-cascade:
-    draft: true
 
 minutes_to_complete: 60
 

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

@@ -1,6 +1,5 @@
 User-agent: *
-Disallow: /install-guides/atp/
-Disallow: /install-guides/asct/
+Disallow:
 
 # Explicitly welcome AI crawlers
 User-agent: GPTBot