chore: fix grammar and spelling (#78)

Author: jbampton

CONTRIBUTING.md

@@ -21,7 +21,7 @@
 
 # Contributing to Apache OpenWhisk
 
-Anyone can contribute to the OpenWhisk project and we welcome your contributions.
+Anyone can contribute to the OpenWhisk project, and we welcome your contributions.
 
 There are multiple ways to contribute: report bugs, improve the docs, and
 contribute code, but you must follow these prerequisites and guidelines:
@@ -50,7 +50,7 @@ Please raise any bug reports or enhancement requests on the respective project r
 list to see if your issue has already been raised.
 
 A good bug report is one that make it easy for us to understand what you were trying to do and what went wrong.
-Provide as much context as possible so we can try to recreate the issue.
+Provide as much context as possible, so we can try to recreate the issue.
 
 A good enhancement request comes with an explanation of what you are trying to do and how that enhancement would help you.
 

README.md

@@ -49,12 +49,12 @@ Node Package Manager:
 ```
 npm install -g openwhisk-composer
 ```
-We recommend to install the package globally (with `-g` option) if you intend to
+We recommend installing the package globally (with `-g` option) if you intend to
 use the `compose` and `deploy` commands to compile and deploy compositions.
 
 ## Defining a composition
 
-A composition is typically defined by means of a Javascript expression as
+A composition is typically defined by means of a JavaScript expression as
 illustrated in [samples/demo.js](samples/demo.js):
 ```javascript
 const composer = require('openwhisk-composer')
@@ -73,7 +73,7 @@ compositions) as parameters. It invokes the first one and, depending on the
 result of this invocation, invokes either the second or third action.
 
  This composition includes the definitions of the three composed actions. If the
- actions are defined and deployed elsewhere, the composition code can be shorten
+ actions are defined and deployed elsewhere, the composition code can be shortened
  to:
 ```javascript
 composer.if('authenticate', 'success', 'failure')

docs/COMBINATORS.md

@@ -29,7 +29,7 @@ The `composer` module offers a number of combinators to define compositions:
 | [`dynamic`](#dynamic) | dynamic invocation | `composer.dynamic()`
 | [`empty`](#empty) | empty sequence | `composer.empty()`
 | [`finally`](#finally) | finalization | `composer.finally('tryThis', 'doThatAlways')` |
-| [`function`](#function) | Javascript function | `composer.function(({ x, y }) => ({ product: x * y }))` |
+| [`function`](#function) | JavaScript function | `composer.function(({ x, y }) => ({ product: x * y }))` |
 | [`if` and `if_nosave`](#if) | conditional | `composer.if('authenticate', 'success', 'failure')` |
 | [`let`](#let) | variable declarations | `composer.let({ count: 3, message: 'hello' }, ...)` |
 | [`literal` or `value`](#literal) | constant value | `composer.literal({ message: 'Hello, World!' })` |
@@ -46,7 +46,7 @@ The `composer` module offers a number of combinators to define compositions:
 | [`while` and `while_nosave`](#while) | loop | `composer.while('notEnough', 'doMore')` |
 
 The `action`, `function`, and `literal` combinators construct compositions
-respectively from OpenWhisk actions, Javascript functions, and constant values.
+respectively from OpenWhisk actions, JavaScript functions, and constant values.
 The other combinators combine existing compositions to produce new compositions.
 
 ## Shorthands
@@ -110,7 +110,7 @@ composer.action('hello', { filename: 'hello.js' })
 composer.action('helloAndBye', { sequence: ['hello', 'bye'] })
 ```
 The action may be defined by providing the code for the action as a string, as a
-Javascript function, or as a file name. Alternatively, a sequence action may be
+JavaScript function, or as a file name. Alternatively, a sequence action may be
 defined by providing the list of sequenced actions. The code (specified as a
 string) may be annotated with the kind of the action runtime.
 
@@ -128,7 +128,7 @@ The `limits` object optionally specifies any combination of:
 
 ### Environment capture in actions
 
-Javascript functions used to define actions cannot capture any part of their
+JavaScript functions used to define actions cannot capture any part of their
 declaration environment. The following code is not correct as the declaration of
 `name` would not be available at invocation time:
 ```javascript
@@ -144,7 +144,7 @@ composer.action('hello', { action: `function main() { return { message: 'Hello '
 
 ## Function
 
-`composer.function(fun)` is a composition with a single Javascript function
+`composer.function(fun)` is a composition with a single JavaScript function
 _fun_. It applies the specified function to the input parameter object for the
 composition.
  - If the function returns a value of type `function`, the composition returns
@@ -313,7 +313,7 @@ if not.
 A _condition_ composition evaluates to true if and only if it produces a JSON
 dictionary with a field `value` with value `true`. Other fields are ignored.
 Because JSON values other than dictionaries are implicitly lifted to
-dictionaries with a `value` field, _condition_ may be a Javascript function
+dictionaries with a `value` field, _condition_ may be a JavaScript function
 returning a Boolean value. An expression such as `params.n > 0` is not a valid
 condition (or in general a valid composition). One should write instead `params
 => params.n > 0`. The input parameter object for the composition is the input

docs/COMMANDS.md

@@ -45,7 +45,7 @@ Flags:
   -v, --version          output the composer version
   --debug LIST           comma-separated list of debug flags (when using --js flag)
 ```
-The `compose` command takes a Javascript module that exports a composition
+The `compose` command takes a JavaScript module that exports a composition
 object (for example [demo.js](../samples/demo.js)) and compiles this object to a
 portable JSON format on the standard output or in file.
 ```

docs/COMPOSITIONS.md

@@ -85,10 +85,10 @@ output parameter objects of `myAction`.
 
 ## Components
 
-Components of a compositions can be actions, Javascript functions, or
+Components of a compositions can be actions, JavaScript functions, or
 compositions.
 
-Javascript functions can be viewed as simple, anonymous actions that do not need
+JavaScript functions can be viewed as simple, anonymous actions that do not need
 to be deployed and managed separately from the composition they belong to.
 Functions are typically used to alter a parameter object between two actions
 that expect different schemas, as in: