Merge pull request ArmDeveloperEcosystem#2613 from pareenaverma/content_review

images renamed

Author: pareenaverma

content/learning-paths/cross-platform/gitlab-managed-runners/_images/gitlag-projects.png renamed to content/learning-paths/cross-platform/gitlab-managed-runners/_images/gitlab-projects.png

@@ -17,15 +17,15 @@ Once we run our pipeline with the correct **`tags`** Gitlab will create everythi
 1. Start by going to the main project page where we will need to Create the CI/CD pipeline.
 
 2. We can choose to create **`.gitlab-ci.yml`** file by using one of the 2 options circled in red in the image below. 
-![CI-CD-New #center](_images/CI-CD-New.png)
+![CI-CD-New #center](_images/ci-cd-new.png)
 
 Option1: We can Click on **`Set up CI/CD`** button/link and follow the wizad to create an empty **`.gitlab-ci.yml`** file.
 
 Option2: Click on the "+" button. From the popup menu click on **`New File`** option and name the file **`.gitlab-ci.yml`** and then click on **`Commit Changes`** button on the top right hand side like in the image below (Add any message as your commit message).
-![New-YML #center](_images/New-YML.png)
+![New-YML #center](_images/new-yml.png)
 
 3. A page like the one in the image below will be visible with our **`.gitlab-ci.yml`** file. From here, we will need to Click on the **`Edit`** button. A menu will pop up, We will click on **`Edit in pipeline Editor`** which will allow us to add our CD/CD script.
-![Editor-YML #center](_images/Editor-YML.png)
+![Editor-YML #center](_images/editor-yml.png)
 
 4. In the pipeline editor, just copy and paste the following YML script and click on commit changes (Add any relevent message as your commit update message).
 ```YML
@@ -87,4 +87,4 @@ deploy-job:      # This job runs in the deploy stage.
     - echo "Deploying application..."
     - echo "Application successfully deployed."
 ```
-5. Once you commit the file updates, Gitlab will check the scripts for errors and will try to execute the pipeline directly. 
+5. Once you commit the file updates, Gitlab will check the scripts for errors and will try to execute the pipeline directly. 

content/learning-paths/cross-platform/gitlab-managed-runners/pipeline.md

@@ -19,19 +19,19 @@ We can also choose to use any previously created projects in our Gitlab account.
 1. From the Home page, Click on the **`Projects`** icon from the menu on the left hand side panel as the image below.  
 
 2. Click on the **`New Project`** button on the top right hand side as the image below.
-![Gitlab-Projects #center](_images/Gitlab-Projects.png)
+![Gitlab-Projects #center](_images/gitlab-projects.png)
 
 3. We will get a new screen like the image below with multiple options. You can choose any of the 2 options highlighted in red from the image below.
 
 {{% notice Note %}}
 If we chose option 2 then we will need to choose **`GitLab CI/CD components`** option from the list of templates.
 {{%/notice%}}
 
-![New-Project #center](_images/New-Project.png)
+![New-Project #center](_images/new-project.png)
 
 4. Regardles of which option we choose, We will get a screen like the image below where we need to fill-in fields highlighted in red. The first field is the **`Project Name`** which we will name it **`CI-CD Runner`**. In the second field we need to choose any option from the **`Project Url`** list then click on the  **`Create Project`** button at the end of the page.
-![Project-Info #center](_images/Project-Info.png) 
+![Project-Info #center](_images/project-info.png) 
 
 ##### **If we did everything correctly then we should get a screen like the one in the image below.**
-![Project-Done #center](_images/Project-Done.png)
+![Project-Done #center](_images/project-done.png)
 

content/learning-paths/cross-platform/gitlab-managed-runners/project.md

@@ -41,16 +41,16 @@ Gitlab offers a lot of documentions on how to create pipeline that fits differen
 ## How to run your pipeline for testing and to check the results:
 
 From the left hand side panel, Navigate to **`Build`** then to **`Pipeline`** then click on **`New pipeline`** button on the top right hand side just like the image below. In the new window click on **`New pipeline`** button again and your pipeline will start to execute.
-![New-Pipeline #center](_images/New-Pipeline.png)
+![New-Pipeline #center](_images/new-pipeline.png)
 
 To check the status of your pipeline and to check the output of any of it's Jobs simply click on any of the **`Jobs`** as the image below (with red rectangle around them).
-![pipeline-execution #center](_images/Pipeline-execution.png)
+![pipeline-execution #center](_images/pipeline-execution.png)
 
 ## Gitlab Helpful tools
 
-If you navigate to your pipeline editor from before you will notice that there are more tabs in that page other than the **`Edit`** tab. ![visual-pipeline #center](_images/Visual-pipeline.png)
+If you navigate to your pipeline editor from before you will notice that there are more tabs in that page other than the **`Edit`** tab. ![visual-pipeline #center](_images/visual-pipeline.png)
 
 ### The other Tabs are:
 
 1. Visualize: which can visulaize your pipeline for you as you edit it's componenets which can be very helpful especially for complex pipelines.
-2. Validate: which can validate your pipeline script as you are editting them and saving from time to time so that you can catch any issues with you code early on.
+2. Validate: which can validate your pipeline script as you are editting them and saving from time to time so that you can catch any issues with you code early on.