Fix minor typo in readmes

concourse-pipeline-hacks/private-docker-registry/README.md

@@ -61,7 +61,7 @@ This article does not provide any recommendation on how to setup a private Docke
    ...
 ```
 
-  Access the Concourse web interface, un-pause the pipeline you just configured and then run it to check if its tasks appropriately download the Docker image from your local registry.
+  Access the Concourse web interface, unpause the pipeline you just configured and then run it to check if its tasks appropriately download the Docker image from your local registry.
 
 
 ## References

concourse-pipeline-patterns/gated-pipelines/01-simple/README.md

@@ -44,7 +44,7 @@ It defines a manual job between two other jobs that are automatically trigger up
 To create the sample pipeline in your concourse server, download file [gated-pipeline-01-simple.yml](gated-pipeline-01-simple.yml) and issue the following fly command:   
 `fly -t <your-concourse-alias> set-pipeline -p simple-gate -c gated-pipeline-01-simple.yml`
 
-You will notice that, once the pipeline is un-paused in Concourse, it will automatically execute its first job (`Run-automatically`). Then, you will have to click on the second job (`Manually-trigger-me`) and click its `+` icon to manually run it. Only then, the second and third jobs will be executed with the corresponding resource version processed by the first job.
+You will notice that, once the pipeline is unpaused in Concourse, it will automatically execute its first job (`Run-automatically`). Then, you will have to click on the second job (`Manually-trigger-me`) and click its `+` icon to manually run it. Only then, the second and third jobs will be executed with the corresponding resource version processed by the first job.
 
 This example illustrates the typical pattern of building and unit testing code in the first half of the CI/CD pipeline and then deploying it to a more tightly controlled environment (the second half of the pipeline) only upon a manual pipeline job trigger by an authorized user.
 

concourse-pipeline-patterns/gated-pipelines/02-shipit/README.md

@@ -25,7 +25,7 @@ To create the sample pipeline in your concourse server:
 ![ShipIt gated pipeline screenshot](https://raw.githubusercontent.com/lsilvapvt/misc-support-files/master/docs/images/shipit-gated-pipeline.png)
 
 
-Once the pipeline is un-paused in Concourse, it will:
+Once the pipeline is unpaused in Concourse, it will:
 
 1. Automatically execute its first two jobs (`Build-It` and `Test-It`) for every new release of the monitored repository
 

concourse-pipeline-patterns/gated-pipelines/03-shipit-enhanced/README.md

@@ -34,7 +34,7 @@ To create the sample pipeline in your concourse server:
 `fly -t <your-concourse-alias> set-pipeline -p shipt-it-enhanced -c gated-pipeline-03-shipit-enhanced.yml -l params.yml`
 
 
-Once the pipeline is un-paused in Concourse, it will:
+Once the pipeline is unpaused in Concourse, it will:
 
 1. Automatically execute the first two jobs (`Build-It` and `Test-It`) for every new release of the monitored repository
 

concourse-pipeline-patterns/time-triggered-pipelines/01-single-time-trigger/README.md

@@ -33,7 +33,7 @@ The pipeline below provides a sample of multiple jobs that are automatically tri
 To create the sample pipeline in your concourse server, download file [scheduled-pipeline-01](scheduled-pipeline-01.yml) and issue the following fly command:   
 `fly -t <your-concourse-alias> set-pipeline -p simple-timer -c scheduled-pipeline-01.yml`
 
-Then un-paused the pipeline in Concourse and it should automatically get triggered within 3 minutes.
+Then unpaused the pipeline in Concourse and it should automatically get triggered within 3 minutes.
 
 
 ### See also

concourse-pipeline-patterns/time-triggered-pipelines/02-multiple-time-triggers/README.md

@@ -22,7 +22,7 @@ To create the sample pipeline in your concourse server:
 1. issue the following fly command:   
 `fly -t <your-concourse-alias> set-pipeline -p multiple-timers -c scheduled-pipeline-02.yml`
 
-Then un-paused the `multiple-timers` pipeline in Concourse and it will be triggered either automatically in the interval of every 4 or every 10 minutes or manually by running job `manual-trigger`.
+Then unpaused the `multiple-timers` pipeline in Concourse and it will be triggered either automatically in the interval of every 4 or every 10 minutes or manually by running job `manual-trigger`.
 
 
 Note:

pipelines/appdev/blue-green-app-deployment/README.md

@@ -75,7 +75,7 @@ _pws-app-domain:_ the domain name used for your CF apps (e.g. cfapps.io)
    __fly -t local login http://192.168.100.4:8080__  
    __fly -t local set-pipeline -c ci/pipeline.yml -p blue-green-pipeline -l ci/credentials.yml__
 
-4. Access to the Concourse web interface (e.g. http://192.168.100.4:8080 ), click on the list of pipelines, un-pause the _blue-green-pipeline_ and then click on its link to visualize its pipeline diagram.
+4. Access to the Concourse web interface (e.g. http://192.168.100.4:8080 ), click on the list of pipelines, unpause the _blue-green-pipeline_ and then click on its link to visualize its pipeline diagram.
 
 You will then notice the pipeline's jobs getting executed within a few seconds, one at a time, if the previous job in the pipeline is executed successfully.
 

pipelines/azure/azure-blobstore-integration/README.md

@@ -113,7 +113,7 @@ jobs:
 3. Configure the sample pipeline in Concourse with the *fly* command:  
    __fly -t <your-concourse-alias> set-pipeline -p azure-blobstore-pipeline -c pipeline.yml__  
 
-4. Access to the Concourse web interface, click on the list of pipelines, un-pause the *azure-blobstore-pipeline* and then click on its link to visualize its pipeline diagram  
+4. Access to the Concourse web interface, click on the list of pipelines, unpause the *azure-blobstore-pipeline* and then click on its link to visualize its pipeline diagram  
 
 5. To execute the pipeline, click on the ```1-build-and-save-release-to-blobstore``` job and then click on the ```+``` sign to execute the pipeline.
 

pipelines/deprecated/pcf-cfops-backup/README.md

@@ -112,7 +112,7 @@ _number-of-days-to-keep-backup-files:_ number of days for old backup files to be
    __fly -t local login http://192.168.100.4:8080__  
    __fly -t local set-pipeline -c ci/pipelines/pipeline.yml -p pcf-cfops-backup -l ci/pipelines/credentials.yml__
 
-4. Access to the Concourse web interface (e.g. http://192.168.100.4:8080 ), click on the list of pipelines, un-pause the _pcf-cfops-backup_ and then click on its link to visualize its pipeline diagram.
+4. Access to the Concourse web interface (e.g. http://192.168.100.4:8080 ), click on the list of pipelines, unpause the _pcf-cfops-backup_ and then click on its link to visualize its pipeline diagram.
 
 As-is, the pipeline's jobs will be automatically executed only after a trigger is generated by the ___time___ resource at night.   
 If you want the job to run right away, change the pipeline definition file ___ci/pipelines/pipeline.yml___ to remove the dependency on the time resource and run the fly command above with the ___set-pipeline___ option.

pipelines/google/google-cloud-storage-integration/README.md

@@ -135,7 +135,7 @@ jobs:
 3. Configure the sample pipeline in Concourse with the *fly* command:  
    __fly -t <your-concourse-alias> set-pipeline -p gcs-bucket-pipeline -c pipeline.yml__  
 
-4. Access to the Concourse web interface, click on the list of pipelines, un-pause the *gcs-bucket-pipeline* and then click on its link to visualize its pipeline diagram  
+4. Access to the Concourse web interface, click on the list of pipelines, unpause the *gcs-bucket-pipeline* and then click on its link to visualize its pipeline diagram  
 
 5. To execute the pipeline, click on the ```1-build-and-save-release-to-gcs``` job and then click on the ```+``` sign to execute the pipeline.
 

pipelines/jfrog/artifactory-integration/README.md

@@ -103,7 +103,7 @@ This pipeline definition file can also be downloaded from [this repository](http
 3. Configure the sample pipeline in Concourse with the *fly* command:  
    __fly -t <your-concourse-alias> set-pipeline -p artifactory-pipeline -c pipeline.yml__  
 
-4. Access to the Concourse web interface, click on the list of pipelines, un-pause the _artifactory-pipeline_ and then click on its link to visualize its pipeline diagram
+4. Access to the Concourse web interface, click on the list of pipelines, unpause the _artifactory-pipeline_ and then click on its link to visualize its pipeline diagram
 5. To execute the pipeline, click on the ```1-build-an-artifact``` job and then click on the ```+``` sign to execute the pipeline.
 
 After job ```1-build-an-artifact``` is executed, you should see a new version of the created file in the Artifactory server. Subsequently, you should see job ```2-trigger-when-new-file-is-added-to-artifactory``` automatically triggered to retrieve that latest file version from Artifactory.

pipelines/notifications/email-with-attachments/README.md

@@ -74,7 +74,7 @@ _```email-to```:_ the list of comma separated destination emails without encodin
 3. Configure the sample pipeline in Concourse with the following commands:  
    __fly -t <your-concourse-alias> set-pipeline -p email-pipeline -c ci/pipeline.yml -l ci/credentials.yml__  
 
-4. Access to the Concourse web interface, click on the list of pipelines, un-pause the _email-pipeline_ and then click on its link to visualize its pipeline diagram
+4. Access to the Concourse web interface, click on the list of pipelines, unpause the _email-pipeline_ and then click on its link to visualize its pipeline diagram
 5. To execute the pipeline, click on the ```send-email-with-attachment``` job and then click on the ```+``` sign to execute the pipeline.
 
 The recipients listed you your ```email-to``` parameter should receive an email shortly after the pipeline is run successfully.

pipelines/notifications/email-with-attachments/build-metadata.md

@@ -24,7 +24,7 @@ Once you have a Concourse server setup to deploy this sample pipeline:
    `fly -t local set-pipeline -p email-with-metadata -c email_with_metadata.yml`  
 
 
-4. Go into the Concourse web interface, un-pause the new pipeline and run the send-email-with-metadata job.
+4. Go into the Concourse web interface, unpause the new pipeline and run the send-email-with-metadata job.
 
 ---
 ### Notes and hints