Correct some typos and indentation

Author: jpbriend

pipeline-template-examples/demos/multibranch-bitbucket-server/README.md

@@ -1,13 +1,13 @@
 # CloudBees Pipeline Templates Example
 ## Multibranch Pipeline Authentication for a Bitbucket Server
 
-This example shows how to add authentication to Bitbucket.org. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
+This example shows how to add authentication to a Bitbucket server. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
 
 ````
 multibranch:
   branchSource:
     bitbucket:
-      remote: https://bitbucket.beescloud.com
+      remote: https://bitbucket.mycompany.com
       repoOwner: myCompany
       repository: ${repoName}
       credentialsId: my-team-bitbucket-credentials

pipeline-template-examples/demos/multibranch-git/README.md

@@ -1,7 +1,7 @@
 # CloudBees Pipeline Templates Example
 ## Multibranch Pipeline Authentication for a Git Server
 
-This example shows how to add authentication to Bitbucket.org. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
+This example shows how to add authentication to your Git server. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
 
 ````
 multibranch:

pipeline-template-examples/demos/multibranch-github-com/README.md

@@ -1,7 +1,7 @@
 # CloudBees Pipeline Templates Example
 ## Multibranch Pipeline Authentication for Github.com
 
-This example shows how to add authentication to Bitbucket.org. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
+This example shows how to add authentication to Github.com. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
 
 ````
 multibranch:

pipeline-template-examples/demos/multibranch-github-ent/README.md

@@ -1,13 +1,13 @@
 # CloudBees Pipeline Templates Example
 ## Multibranch Pipeline Authentication for Github Enterprise
 
-This example shows how to add authentication to Bitbucket.org. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
+This example shows how to add authentication to your Github Enterprise instance. The developer will supply the value for the ${repoName} parameter when they create their pipeline job in CloudBees Core, and Pipeline Templates then use the developer's value to replace the placeholder variable in the Jenkinsfile.
 
 ````
 multibranch:
   branchSource:
     github:
-      apiUrl: https://github.beescloud.com/api/v3
+      apiUrl: https://github.mycompany.com/api/v3
       repoOwner: myCompany
       repository: ${repoName}
       credentialsId: my-team-github-credentials

pipeline-template-examples/templates/simple-java-maven-app/Jenkinsfile

@@ -16,27 +16,27 @@ pipeline {
 
     post {
 
-    // Email Ext plugin: 
-    success {  
-      
-      emailext (
-          subject: "SUCCESSFUL: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
-          body: """<p>SUCCESSFUL: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':</p>
-            <p>Check console output at &QUOT;<a href='${env.BUILD_URL}'>${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>&QUOT;</p>""",
-          to: "${emailRecipient}",
-          from: "buildNotifications@emailaddress.com"
-        )
-    }
+      // Email Ext plugin: 
+      success {  
+        
+        emailext (
+            subject: "SUCCESSFUL: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
+            body: """<p>SUCCESSFUL: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':</p>
+              <p>Check console output at &QUOT;<a href='${env.BUILD_URL}'>${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>&QUOT;</p>""",
+            to: "${emailRecipient}",
+            from: "buildNotifications@emailaddress.com"
+          )
+      }
 
-    failure {
-      
-      emailext (
-          subject: "FAILED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
-          body: """<p>FAILED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':</p>
-            <p>Check console output at &QUOT;<a href='${env.BUILD_URL}'>${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>&QUOT;</p>""",
-          to: "${emailRecipient}",
-          from: "buildNotifications@emailaddress.com"
-        )
-    }
+      failure {
+        
+        emailext (
+            subject: "FAILED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
+            body: """<p>FAILED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':</p>
+              <p>Check console output at &QUOT;<a href='${env.BUILD_URL}'>${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>&QUOT;</p>""",
+            to: "${emailRecipient}",
+            from: "buildNotifications@emailaddress.com"
+          )
+      }
   }
 }