Merge pull request #241 from tasha-m-k/master

Making wording more consistent.

Author: markcocker

CONTRIBUTING.md

@@ -7,15 +7,15 @@ This project welcomes all contributions.
 - If you would like to contribute a bug fix or small enhancement, please fork the repo and make a pull request.
 - If you would like to contribute a new feature, please raise an issue describing your proposal so we can discuss it first.
 
-## Developing Zowe CLI plugins
+## Developing Zowe CLI plug-ins
 
 For guidelines on developing Zowe CLI plug-ins see the [Zowe CLI GitHub repository](https://github.com/zowe/zowe-cli). The following information is critical to working with the code, running/writing/maintaining automated tests, developing consistent syntax and ensuring that the plug-in integrates with Zowe CLI properly:
 
 | For more information about ... | See: |
 | ------------------------------ | ----- |
-| General guidelines that apply to contributing to Zowe CLI and Plug-ins | [Contribution Guidelines](https://github.com/zowe/zowe-cli/blob/master/CONTRIBUTING.md) |
+| General guidelines that apply to contributing to Zowe CLI and plug-ins | [Contribution Guidelines](https://github.com/zowe/zowe-cli/blob/master/CONTRIBUTING.md) |
 | Conventions and best practices for creating packages and plug-ins for Zowe CLI | [Package and Plug-in Guidelines](https://github.com/zowe/zowe-cli/blob/master/docs/PackagesAndPluginGuidelines.md)|
 | Guidelines for running tests on Zowe CLI | [Testing Guidelines](https://github.com/zowe/zowe-cli/blob/master/docs/TESTING.md) |
 | Guidelines for running tests on the plug-ins that you build for Zowe CLI | [Plug-in Testing Guidelines](https://github.com/zowe/zowe-cli/blob/master/docs/PluginTESTINGGuidelines.md) |
 | Documentation that describes the features of the Imperative CLI Framework | [About Imperative CLI Framework](https://github.com/zowe/imperative/wiki) |
-Versioning conventions for Zowe CLI and Plug-ins| [Versioning Guidelines](https://github.com/zowe/zowe-cli/blob/master/docs/MaintainerVersioning.md) |
+Versioning conventions for Zowe CLI and plug-ins| [Versioning Guidelines](https://github.com/zowe/zowe-cli/blob/master/docs/MaintainerVersioning.md) |

README.md

@@ -7,7 +7,7 @@ The project was started in February 2019 and is at an early stage of development
 To try it out, build the plug-in from source as described in [setup](docs-internal/tutorials/Setup.md).
 
 ## Documentation
-You can find information and tutorials on using this plugin in our [documentation](https://ibm.github.io/zowe-cli-cics-deploy-plugin/index.html).
+You can find information and tutorials on using this plug-in in our [documentation](https://ibm.github.io/zowe-cli-cics-deploy-plugin/index.html).
 
 ## Contributing
 Contributions are welcome - see the [contribution guidelines](CONTRIBUTING.md). If you have a question or encounter a problem please raise an issue in this repo.

docs/pages/cdp/cdp-Deploying-your-first-nodejs-app.md

@@ -15,7 +15,7 @@ CICS TS V5.5 introduced support to run Node.js applications and is required by t
 
 ### Procedure
 
-1. Install the Zowe CLI and cics-deploy plugin by following the steps in [Installing](cdp-Installing).
+1. Install the Zowe CLI and cics-deploy plug-in by following the steps in [Installing](cdp-Installing).
 
 2. Create Zowe CLI profiles for z/OSMF, SSH, cics-deploy and CICS by following the steps in [Creating Zowe CLI profiles](cdp-Creating-Zowe-CLI-profiles).
 
@@ -29,19 +29,19 @@ CICS TS V5.5 introduced support to run Node.js applications and is required by t
    npm start
    ```
 
-   The Node.js application will start. You can call the application from a browser using URL [http://localhost:3000/](http://localhost:3000/). To stop the application in the console press CTRL+C.
+   The Node.js application will start. You can call the application from a browser by using URL [http://localhost:3000/](http://localhost:3000/). To stop the application in the console press CTRL+C.
 
 4. Package the Node.js application into a [CICS bundle](cdp-cics-bundles).
 
-    Make sure you are in the root directory of the application.
+    Make sure that you are in the root directory of the application.
 
     Replace the value for `--port` with one that is available for use by the CICS region on z/OS. This sets the PORT environment variable in the generated `.profile` file. Additional variables can be set by editing this file.
 
    ```console
     zowe cics-deploy generate bundle --port 3000 --overwrite
    ```
 
-    The output will indicates the directories and files created to form a CICS bundle. For example:
+    The output indicates the directories and files that are created to form a CICS bundle. For example:
 
     <pre class="messageText">
     define : NODEJSAPP "myexpressapp" with startscript "./bin/www"
@@ -61,13 +61,13 @@ CICS TS V5.5 introduced support to run Node.js applications and is required by t
 
     A progress bar is shown with status messages as the CICS bundle is deployed and the application is started. This can take a few minutes. If there are errors, retry with the `--verbose` option for more detailed output, or refer to [Troubleshooting](cdp-Troubleshooting-General).
 
-    This results in a CICS BUNDLE resource named `Express` being defined, installed and enabled in CICS. If the BUNDLE `Express` was already defined or installed in CICS, it is undeployed first. As the BUNDLE is enabled, the Node.js application is started.
+    This results in a CICS BUNDLE resource named `Express` being defined, installed, and enabled in CICS. If the BUNDLE `Express` was already defined or installed in CICS, it is undeployed first. As the BUNDLE is enabled, the Node.js application is started.
 
 6. Test the Node.js application.
 
-    You can call the application from a browser using URL [http://myzos:3000/](http://myzos:3000/), replacing _myzos_ with the host name of the z/OS system, and _3000_ with the port specified in step 4.
+    You can call the application from a browser by using URL [http://myzos:3000/](http://myzos:3000/), replacing _myzos_ with the host name of the z/OS system, and _3000_ with the port specified in step 4.
 
-    If you make changes to the application you can redeploy it by repeating step 5.
+    If you make changes to the application, you can redeploy it by repeating step 5.
 
 ### Results
 

docs/pages/cdp/cdp-Home.md

@@ -1,16 +1,16 @@
 ---
-title: Zowe CLI CICS deploy plugin
+title: Zowe CLI CICS deploy plug-in
 tags: [getting_started]
 keywords:
-summary: "The Zowe command line interface (CLI) provides a simple and streamlined way to interact with IBM z/OS. The cics-deploy plugin extends the Zowe CLI to deploy applications developed on a workstation to IBM CICS Transaction Server for z/OS (CICS)."
+summary: "The Zowe command line interface (CLI) provides a simple and streamlined way to interact with IBM z/OS. The cics-deploy plug-in extends the Zowe CLI to deploy applications developed on a workstation to IBM CICS Transaction Server for z/OS (CICS)."
 sidebar: cdp_sidebar
 permalink: index.html
 folder: cdp
 ---
 
 It provides a CICS deployment workflow for developers and CI/CD automation pipelines similar to that experienced when deploying applications to cloud environments.
 
-Before you start, and especially if you are not familiar with the world of z/OS, Zowe and CICS, it's a good idea to read about some of the key concepts, which include [Zowe](cdp-zowe-and-cli), [Zowe CLI profiles](cdp-zowe-profiles) and [CICS bundles](cdp-cics-bundles). If you're keen to get going quickly, you can jump right in and follow along with our tutorial on [Deploying your first Node.js app](cdp-Deploying-your-first-nodejs-app).
+Before you start, and especially if you are not familiar with the world of z/OS, Zowe, and CICS, it's a good idea to read about some of the key concepts, which include [Zowe](cdp-zowe-and-cli), [Zowe CLI profiles](cdp-zowe-profiles) and [CICS bundles](cdp-cics-bundles). If you're keen to get going quickly, you can jump right in and follow along with our tutorial on [Deploying your first Node.js app](cdp-Deploying-your-first-nodejs-app).
 
 When everything is [installed](cdp-Installing) and you have [created the Zowe CLI profiles](cdp-Creating-Zowe-CLI-profiles), you can deploy an application from your workstation to CICS in two steps:
 

docs/pages/cdp/cdp-Installing.md

@@ -2,7 +2,7 @@
 title: Installing
 tags: [getting_started]
 keywords:
-summary: "To install the Zowe CLI and cics-deploy plugin, perform the following steps. For clarity, these components are installed on your local workstation, not on z/OS."
+summary: "To install the Zowe CLI and cics-deploy plug-in, perform the following steps. For clarity, these components are installed on your local workstation, not on z/OS."
 sidebar: cdp_sidebar
 permalink: cdp-Installing.html
 folder: cdp
@@ -18,13 +18,13 @@ toc: false
     npm --version
     ```
 
-2. Install [Zowe CLI](https://zowe.github.io/docs-site/latest/user-guide/cli-installcli.html). For example to install using npm:
+2. Install [Zowe CLI](https://zowe.github.io/docs-site/latest/user-guide/cli-installcli.html). For example, to install using npm:
 
     ```console
     sudo npm install -g @zowe/cli
     ```
 
-3. Build and install the cics-deploy plugin as described in [Setting up your development environment](https://github.com/IBM/zowe-cli-cics-deploy-plugin/blob/master/docs-internal/tutorials/Setup.md). For example:
+3. Build and install the cics-deploy plug-in as described in [Setting up your development environment](https://github.com/IBM/zowe-cli-cics-deploy-plugin/blob/master/docs-internal/tutorials/Setup.md). For example:
 
     ```console
     mkdir ~/cics-deploy
@@ -37,7 +37,7 @@ toc: false
     zowe plugins install .
     ```
 
-4. Verify the plugin is installed:
+4. Verify the plug-in is installed:
 
     ```console
     zowe plugins list

docs/pages/cdp/cdp-Requirements.md

@@ -2,7 +2,7 @@
 title: Requirements on z/OS
 tags: [getting_started, requirements]
 keywords:
-summary: "The cics-deploy plugin is dependent on several servers and facilities that need to be set up on z/OS."
+summary: "The cics-deploy plug-in is dependent on several servers and facilities that need to be set up on z/OS."
 sidebar: cdp_sidebar
 permalink: cdp-Requirements.html
 folder: cdp

docs/pages/cdp/cdp-Troubleshooting-General.md

@@ -9,7 +9,7 @@ folder: cdp
 ---
 
 ### Console output
-All Zowe CLI cics deploy plugin commands send output to the console when invoked. Very often, enough information is provided for you to diagnose and pinpoint the cause of a problem. The commands `cics-deploy push`, `cics-deploy deploy` and `cics-deploy undeploy` accept a `--verbose` command-line option which can generate extra information if needed.  
+All Zowe CLI CICS deploy plug-in commands send output to the console when invoked. Very often, enough information is provided for you to diagnose and pinpoint the cause of a problem. The commands `cics-deploy push`, `cics-deploy deploy` and `cics-deploy undeploy` accept a `--verbose` command-line option which can generate extra information if needed.  
 
 ### zowe.log
 The .zowe directory on your local workstation contains log files, profiles, and plug-ins. The location of this directory can be customised as described in [ Setting the Zowe CLI home directory](https://zowe.github.io/docs-site/latest/user-guide/cli-configuringcli.html#setting-the-zowe-cli-home-directory) and logging level set as described in [Setting Zowe CLI log levels](https://zowe.github.io/docs-site/latest/user-guide/cli-configuringcli.html#setting-zowe-cli-log-levels).

docs/pages/cdp/cdp-zowe-and-cli.md

@@ -1,5 +1,5 @@
 ---
-title: Zowe, the Zowe CLI and the cics-deploy plugin
+title: Zowe, the Zowe CLI and the cics-deploy plug-in
 tags: [getting_started, concepts]
 keywords:
 summary: "Zowe is an open source framework that bridges the divide between workstation and mainframe computing."
@@ -26,5 +26,5 @@ It allows developers to interact with the mainframe via a command-line interface
 
 The Zowe CLI is extended by creating and installing plug-ins.
 
-### Zowe CLI CICS deploy plugin
-The Zowe CLI CICS deploy plugin extends the Zowe CLI to offer a command-line mechanism for Node.js developers to deploy workstation-developed applications into a running CICS Transaction Server for z/OS region on a remote mainframe. It's the quickest way to get a Node.js application from your workstation into a running CICS region without any special CICS knowledge.
+### Zowe CLI CICS deploy plug-in
+The Zowe CLI CICS deploy plug-in extends the Zowe CLI to offer a command-line mechanism for Node.js developers to deploy workstation-developed applications into a running CICS Transaction Server for z/OS region on a remote mainframe. It is the quickest way to get a Node.js application from your workstation into a running CICS region without any special CICS knowledge.