Refactor Jenkins documentation for clarity and consistency across multiple files

Author: madeline-underwood

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

@@ -1,9 +1,5 @@
 ---
-title: Deploy Jenkins on Arm cloud platforms
-
-draft: true
-cascade:
-    draft: true
+title: Deploy and validate Jenkins on Arm cloud servers
 
 minutes_to_complete: 30   
 

content/learning-paths/servers-and-cloud-computing/jenkins/azure-installation.md

@@ -6,6 +6,8 @@ weight: 5
 layout: learningpathall
 ---
 
+## Install Jenkins on Azure Ubuntu Arm64
+
 To install Jenkins on an Azure Ubuntu 24.04 LTS Arm64 virtual machine, follow these steps.
 
 At the end of the installation, Jenkins is:
@@ -103,4 +105,13 @@ The output is similar to:
 2.528.3
 ```
 
-Jenkins LTS is now successfully deployed on your Azure Ubuntu Arm64 virtual machine.
+## What you've accomplished and what's next
+
+You've successfully installed Jenkins LTS on your Azure Ubuntu Arm64 virtual machine. Your installation includes:
+
+- Jenkins service running and enabled for automatic startup
+- Java 17 runtime properly configured
+- Jenkins accessible on port 8080
+- Arm64-native deployment ready for CI/CD workloads
+
+Next, you'll configure firewall rules to allow external access to Jenkins.

content/learning-paths/servers-and-cloud-computing/jenkins/azure-instance.md

@@ -6,6 +6,8 @@ weight: 3
 layout: learningpathall
 ---
 
+## Create an Arm-based Azure virtual machine using Cobalt 100
+
 You can create an Arm-based Cobalt 100 virtual machine using the Microsoft Azure console, the Azure CLI tool, or Infrastructure as Code (IaC). For this Learning Path, you use the Azure console to create a virtual machine with an Arm-based Cobalt 100 processor. 
 
 You'll focus on the general-purpose virtual machine of the D series. For more details, see [Dpsv6 size series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dpsv6-series) in the Microsoft Azure documentation.  
@@ -16,31 +18,31 @@ If you haven't used Microsoft Azure before, see [Create a Linux virtual machine
 
 To create an Azure virtual machine based on Cobalt 100, launch the Azure portal and navigate to **Virtual Machines**.
 
-1. Select **Create**, and click on **Virtual Machine** from the drop-down list.
-2. In the **Basic** tab, fill in the instance details such as **Virtual machine name** and **Region**.
-3. Choose the image for your virtual machine (for example, **Ubuntu 24.04 LTS**) and select **Arm64** as the VM architecture.
-4. In the **Size** field, click on **See all sizes** and select the **D-Series v6** family of virtual machines. Select **D4ps_v6** from the list.
+* Select **Create**, and click on **Virtual Machine** from the drop-down list.
+* In the **Basic** tab, fill in the instance details such as **Virtual machine name** and **Region**.
+* Choose the image for your virtual machine (for example, **Ubuntu 24.04 LTS**) and select **Arm64** as the VM architecture.
+* In the **Size** field, select **See all sizes** and select the **D-Series v6** family of virtual machines. Select **D4ps_v6** from the list.
 
-![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance.png "Figure 1: Select the D-Series v6 family of virtual machines")
+![Azure portal showing VM size selection with D-Series v6 family and D4ps_v6 instance type highlighted alt-txt#center](images/instance.png "Select the D-Series v6 family of virtual machines")
 
-5. Select **SSH public key** as an authentication type. Azure automatically generates an SSH key pair for you and allows you to store it for future use.
-6. Fill in the administrator username for your virtual machine.
-7. Select **Generate new key pair**, and select **RSA SSH Format** as the SSH key type. RSA offers better security with keys longer than 3072 bits. Give a key pair name to your SSH key.
-8. In **Inbound port rules**, select **HTTP (80)** and **SSH (22)** as the inbound ports.
+* Select **SSH public key** as an authentication type. Azure automatically generates an SSH key pair for you and allows you to store it for future use.
+* Fill in the administrator username for your virtual machine.
+* Select **Generate new key pair**, and select **RSA SSH Format** as the SSH key type. RSA offers better security with keys longer than 3072 bits. Give a key pair name to your SSH key.
+* In **Inbound port rules**, select **HTTP (80)** and **SSH (22)** as the inbound ports.
 
-![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance1.png "Figure 2: Allow inbound port rules")
+![Azure portal VM configuration page showing inbound port rules section with HTTP and SSH ports selected alt-txt#center](images/instance1.png "Allow inbound port rules")
 
-9. Click on the **Review + Create** tab and review the configuration for your virtual machine.
+Select the **Review + Create** tab and review the configuration for your virtual machine.
 
-![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/ubuntu-pro.png "Figure 3: Review and Create an Azure Cobalt 100 Arm64 VM")
+![Azure portal review page showing complete VM configuration including Ubuntu 24.04 LTS ARM64 image and D4ps_v6 size alt-txt#center](images/ubuntu-pro.png "Review and Create an Azure Cobalt 100 Arm64 VM")
 
-10. When you're confident about your selection, click on the **Create** button, and click on the **Download Private key and Create Resources** button.
+When you're confident about your selection, select the **Create** button, and select the **Download Private key and Create Resources** button.
 
-![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance4.png "Figure 4: Download Private key and Create Resources")
+![Azure portal dialog box prompting to download the SSH private key with filename shown alt-txt#center](images/instance4.png "Download Private key and Create Resources")
 
-11. Your virtual machine is ready and running in a few minutes. Press **Go to Resource** to view the new virtual machine details. You can SSH into the virtual machine using the private key and the public IP address.
+Your virtual machine is ready and running in a few minutes. Press **Go to Resource** to view the new virtual machine details. You can SSH into the virtual machine using the private key and the public IP address.
 
-![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/final-vm.png "Figure 5: VM deployment confirmation in Azure portal")
+![Azure portal showing deployed VM overview page with status as running and public IP address visible alt-txt#center](images/final-vm.png "VM deployment confirmation in Azure portal")
 
 {{% notice Note %}}
 

content/learning-paths/servers-and-cloud-computing/jenkins/azure_firewall.md

@@ -7,11 +7,11 @@ weight: 4
 layout: learningpathall
 ---
 
+## Configure Azure firewall for Jenkins
+
 To allow external traffic on port 8080 for your application running on an Azure virtual machine, open the port in the Network Security Group (NSG) attached to the virtual machine's network interface or subnet.
 
-{{% notice Note %}}
-For more information about Azure setup, see [Getting started with Microsoft Azure Platform](/learning-paths/servers-and-cloud-computing/csp/azure/).
-{{% /notice %}}
+{{% notice Note %}} For more information about Azure setup, see [Getting started with Microsoft Azure Platform](/learning-paths/servers-and-cloud-computing/csp/azure/).{{% /notice %}}
 
 
 ## Create a firewall rule in Azure
@@ -20,18 +20,18 @@ To expose the TCP port 8080, create a firewall rule.
 
 Navigate to the [Azure Portal](https://portal.azure.com), go to **Virtual Machines**, and select your virtual machine.
 
-![Create a firewall rule alt-text#center](images/virtual_machine.png "Virtual Machines")
+![Azure portal Virtual Machines page showing list of running VMs with details like status, location, and size alt-txt#center](images/virtual_machine.png "Virtual Machines")
 
-In the left menu, click **Networking** and in the **Networking** select **Network settings** that is associated with the virtual machine's network interface.
+In the left menu, select **Networking** and in the **Networking** select **Network settings** that is associated with the virtual machine's network interface.
 
-![Create a firewall rule alt-text#center](images/networking.png "Network settings")
+![Azure portal Network settings page showing network interface and security group configuration alt-txt#center](images/networking.png "Network settings")
 
 Navigate to **Create port rule**, and select **Inbound port rule**.
 
-![Create a firewall rule alt-text#center](images/port_rule.png "Create rule")
+![Azure portal showing Create port rule dropdown with Inbound port rule option highlighted alt-txt#center](images/port_rule.png "Create rule")
 
-Configure it using the following details. After filling in the details, click **Add** to save the rule.
+Configure it using the following details. After filling in the details, select **Add** to save the rule.
 
-![Create a firewall rule alt-text#center](images/inbound_rule.png "Network settings")
+![Azure portal inbound security rule configuration form showing port 8080, TCP protocol, and Allow action alt-txt#center](images/inbound_rule.png "Network settings")
 
 The network firewall rule is now created.

content/learning-paths/servers-and-cloud-computing/jenkins/baseline.md

@@ -6,6 +6,8 @@ weight: 9
 layout: learningpathall
 ---
 
+## Validate Jenkins installation on Arm64
+
 After installation completes, validate the Jenkins LTS setup on the Azure Ubuntu 24.04 Arm64 virtual machine. You'll verify service health, network access, Arm architecture, and run a first pipeline.
 
 ## Verify network configuration
@@ -86,19 +88,19 @@ http://<VM_PUBLIC_IP>:8080
 
 Complete the initial Jenkins setup using the web interface:
 
-1. Paste the initial admin password saved previously.
+Paste the initial admin password saved previously.
 
-![ Jenkins UI alt-text#center](images/initial-setup.png "Figure 1: Initial Jenkins page")
+![Jenkins web interface showing unlock page with text field for entering initial admin password alt-txt#center](images/initial-setup.png "Initial Jenkins page")
 
-2. Select **Install suggested plugins**.
+Select **Install suggested plugins**.
 
-![ Jenkins UI alt-text#center](images/jenkins-plugins.png "Figure 2: Install suggested plugins")
+![Jenkins setup wizard showing plugin installation screen with progress indicators for multiple plugins being installed alt-txt#center](images/jenkins-plugins.png "Install suggested plugins")
 
-3. Create an admin user.
+Create an admin user.
 
-![ Jenkins UI alt-text#center](images/jenkins-admin.png "Figure 3: Create admin user")
+![Jenkins user creation form with fields for username, password, full name, and email address alt-txt#center](images/jenkins-admin.png "Create admin user")
 
-4. Finish setup and reach the Jenkins dashboard.
+Finish setup and reach the Jenkins dashboard.
 
 ## Execute a first Jenkins pipeline
 
@@ -114,18 +116,18 @@ http://<VM_PUBLIC_IP>:8080
 
 Log in using your Jenkins credentials:
 
-![ Jenkins UI alt-text#center](images/jenkins-login-page.png "Figure 4: Jenkins login page")
+![Jenkins login screen with username and password fields and Sign in button alt-txt#center](images/jenkins-login-page.png "Jenkins login page")
 
 ### Create a new pipeline job
 
 Create a basic pipeline job to validate execution capability:
 
-1. Click **New Item** (left sidebar).
-2. Enter item name: `armbaseline-pipeline`.
-3. Select **Pipeline**.
-4. Click **OK**.
+* Click **New Item** (left sidebar).
+* Enter item name: `armbaseline-pipeline`.
+* Select **Pipeline**.
+* Select **OK**.
 
-![ Jenkins UI alt-text#center](images/jenkins-item.png "Figure 5: Create new pipeline item")
+![Jenkins New Item page showing item name field with armbaseline-pipeline entered and Pipeline option selected alt-txt#center](images/jenkins-item.png "Create new pipeline item")
 
 ### Add the pipeline script
 
@@ -155,27 +157,27 @@ pipeline {
 }
 ```
 
-Click **Save**.
+Select **Save**.
 
-![Jenkins UI alt-text#center](images/jenkins-pipeline.png "Figure 6: Create pipeline")
+![Jenkins pipeline configuration page showing Pipeline script definition section with Groovy code visible alt-txt#center](images/jenkins-pipeline.png "Create pipeline")
 
 ### Run the pipeline
 
 Trigger the pipeline execution:
 
-1. On the job page, click **Build Now**.
-2. A build number appears under **Build History**.
+* On the job page, select **Build Now**.
+* A build number appears under **Build History**.
 
-![ Jenkins UI alt-text#center](images/jenkins-job.png "Figure 7: Run pipeline")
+![Jenkins pipeline job page showing Build Now button in left sidebar and build #1 appearing in Build History alt-txt#center](images/jenkins-job.png "Run pipeline")
 
 ### View console output
 
 Review the pipeline logs to confirm successful execution:
 
-1. Click the build number (for example, `#1`).
-2. Click **Console Output**.
+* Select the build number (for example, `#1`).
+* Select **Console Output**.
 
-![Jenkins UI alt-text#center](images/jenkins-output.png "Figure 8: Console output")
+![Jenkins console output displaying pipeline execution logs showing Architecture aarch64 and Java version information alt-txt#center](images/jenkins-output.png "Console output")
 
 ## What you've accomplished and what's next
 

content/learning-paths/servers-and-cloud-computing/jenkins/gcp-installation.md

@@ -6,6 +6,8 @@ weight: 8
 layout: learningpathall
 ---
 
+## Install Jenkins on GCP SUSE Arm64
+
 To install Jenkins (Stable LTS) on a GCP SUSE Linux Enterprise Server (SLES) Arm64 virtual machine, follow these steps.
 
 ## Update the system and install utilities
@@ -97,4 +99,13 @@ The output is similar to:
 2.528.3
 ```
 
-Jenkins LTS is now successfully installed on your GCP SUSE Arm64 virtual machine.
+## What you've accomplished and what's next
+
+You've successfully installed Jenkins LTS on your GCP SUSE Arm64 virtual machine. Your installation includes:
+
+- Jenkins service running and enabled for automatic startup
+- Java 17 runtime properly configured
+- Jenkins accessible on port 8080
+- Arm64-native deployment ready for CI/CD workloads
+
+Next, you'll validate the Jenkins installation and run your first pipeline.

content/learning-paths/servers-and-cloud-computing/jenkins/gcp-instance.md

@@ -6,13 +6,13 @@ weight: 7
 layout: learningpathall
 ---
 
-You now provision a Google Axion C4A virtual machine on Google Cloud Platform (GCP) using the `c4a-standard-4` machine type, which provides 4 vCPUs and 16 GB of memory.
+## Create a Google Axion C4A virtual machine
 
-{{% notice Note %}}
-For general guidance on setting up a Google Cloud account and project, see [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).
-{{% /notice %}}
+Provision a Google Axion C4A virtual machine on Google Cloud Platform (GCP) using the `c4a-standard-4` machine type, which provides 4 vCPUs and 16 GB of memory.
 
-## Provision a Google Axion C4A virtual machine in the Google Cloud Console
+{{% notice Note %}}For general guidance on setting up a Google Cloud account and project, see [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).{{% /notice %}}
+
+### Use the Google Cloud console to create the VM
 
 To create a virtual machine using the C4A instance type:
 
@@ -23,7 +23,7 @@ To create a virtual machine using the C4A instance type:
   - Set **Series** to **C4A**.
   - Select **c4a-standard-4** as the machine type.
 
-![Google Cloud Console VM creation page with C4A machine series selected alt-text#center](images/gcp-vm.png "Creating a Google Axion C4A virtual machine in the Google Cloud Console")
+![Google Cloud Console VM creation page showing machine configuration section with C4A series and c4a-standard-4 machine type selected alt-txt#center](images/gcp-vm.png "Creating a Google Axion C4A virtual machine in the Google Cloud Console")
 
 - Under **OS and storage**, select **Change**, and then choose an Arm64-based operating system image.
   - For this Learning Path, select **SUSE Linux Enterprise Server**.
@@ -33,12 +33,12 @@ To create a virtual machine using the C4A instance type:
 - Under **Networking**, enable **Allow HTTP traffic** and **Allow HTTPS traffic**. Additionally, enter **"allow-tcp-8080"** as a networking tag.
 - Select **Create** to launch the virtual machine.
 
-After the instance starts, click **SSH** next to the virtual machine in the instance list to open a browser-based terminal session.
+After the instance starts, select **SSH** next to the virtual machine in the instance list to open a browser-based terminal session.
 
-![Google Cloud Console VM instances list with SSH button highlighted alt-text#center](images/gcp-ssh.png "Connecting to a running C4A instance using SSH")
+![Google Cloud Console VM instances page showing running instance with SSH button next to the instance name alt-txt#center](images/gcp-ssh.png "Connecting to a running C4A instance using SSH")
 
 A new browser window opens with a terminal connected to your virtual machine.
 
-![Browser-based terminal window showing a command prompt on a SUSE Linux virtual machine alt-text#center](images/gcp-shell.png "Terminal session connected to the virtual machine")
+![Browser window displaying SSH terminal session with SUSE Linux command prompt showing username and hostname alt-txt#center](images/gcp-shell.png "Terminal session connected to the virtual machine")
 
 Next, install Jenkins on your virtual machine.

content/learning-paths/servers-and-cloud-computing/jenkins/gcp_firewall.md

@@ -6,33 +6,33 @@ weight: 6
 layout: learningpathall
 ---
 
+## Configure GCP firewall for Jenkins
+
 To allow inbound TCP traffic on port 8080, create a firewall rule in the Google Cloud Console.
 
-{{% notice Note %}}
-For more information about GCP setup, see [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).
-{{% /notice %}}
+{{% notice Note %}} For more information about GCP setup, see [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).{{% /notice %}}
 
 ## Create a firewall rule in GCP
 
 To expose the TCP port 8080, create a firewall rule.
 
 Navigate to the [Google Cloud Console](https://console.cloud.google.com/), go to **VPC Network > Firewall**, and select **Create firewall rule**.
 
-![Create a firewall rule alt-text#center](images/firewall-rule1.png "Create a firewall rule")
+![Google Cloud Console VPC Network Firewall page showing existing firewall rules and Create Firewall Rule button alt-txt#center](images/firewall-rule1.png "Create a firewall rule")
 
 Next, create the firewall rule that exposes the TCP port 8080.
 Set the **Name** of the new rule to "allow-tcp-8080". Select your network that you intend to bind to your VM (default is "autoscaling-net", but your organization might have others).
 
 Set **Direction of traffic** to "Ingress". Set **Allow on match** to "Allow" and **Targets** to "Specified target tags".
 
-![Create a firewall rule alt-text#center](images/network-rule2.png "Creating the TCP/8080 firewall rule")
+![Google Cloud Console firewall rule creation form showing name field, network selection, direction set to Ingress, and targets set to Specified target tags alt-txt#center](images/network-rule2.png "Creating the TCP/8080 firewall rule")
 
 Next, enter "allow-tcp-8080" in the **Target tags** text field. Set **Source IPv4 ranges** to "0.0.0.0/0".
 
-![Create a firewall rule alt-text#center](images/network-rule3.png "Creating the TCP/8080 firewall rule")
+![Google Cloud Console firewall rule form showing target tags field with allow-tcp-8080 entered and source IPv4 ranges set to 0.0.0.0/0 alt-txt#center](images/network-rule3.png "Creating the TCP/8080 firewall rule")
 
-Finally, select **Specified protocols and ports** under the **Protocols and ports** section. Select the **TCP** checkbox, enter "8080" in the **Ports** text field, and select **Create**.
+Finally, select **Specified protocols and ports** under the **Protocols and ports** section. Select the **TCP** checkbox, enter "8080" in the **Ports" text field, and select **Create**.
 
-![Specifying the TCP port to expose alt-text#center](images/network-port.png "Specifying the TCP port to expose")
+![Google Cloud Console firewall rule form showing protocols and ports section with TCP selected and port 8080 specified alt-txt#center](images/network-port.png "Specifying the TCP port to expose")
 
 The network firewall rule is now created, and you can continue with the VM creation.