Small spelling fixes (#360)

Signed-off-by: Tihomir Surdilovic <[email protected]>

Author: tsurdilo

README.md

@@ -9,7 +9,7 @@
 </p>
 
 A specification that defines a vendor-neutral and declarative workflow language,
-targeting the serverless computing technology domain.
+targeting the Serverless computing technology domain.
 
 Serverless Workflow is hosted by the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/) and was approved as a 
 Cloud Native Sandbox level project on July 14, 2020.

examples/README.md

@@ -13,7 +13,7 @@ Provides Serverless Workflow language examples
 - [Applicant Request Decision (Data-based Switch + SubFlows)](#Applicant-Request-Decision-Example)
 - [Provision Orders (Error Handling)](#Provision-Orders-Example)
 - [Monitor Job for completion (Polling)](#Monitor-Job-Example)
-- [Send CloudEvent on Workflow Completion](#Send-CloudEvent-On-Workfow-Completion-Example)
+- [Send CloudEvent on Workflow Completion](#Send-CloudEvent-On-Workflow-Completion-Example)
 - [Monitor Patient Vital Signs (Event state)](#Monitor-Patient-Vital-Signs-Example)
 - [Finalize College Application (Event state)](#Finalize-College-Application-Example)
 - [Perform Customer Credit Check (Callback state)](#Perform-Customer-Credit-Check-Example)
@@ -655,7 +655,7 @@ period, the workflow transitions to the "HandleNoVisaDecision" state.
       "type": "operation",
       "actions": [
         {
-          "subFlowRef": "handleNoVisaDecisionWorkfowId" 
+          "subFlowRef": "handleNoVisaDecisionWorkflowId" 
         }
       ],
       "end": true
@@ -704,7 +704,7 @@ states:
 - name: HandleNoVisaDecision
   type: operation
     actions:
-      - subFlowRef: handleNoVisaDecisionWorkfowId
+      - subFlowRef: handleNoVisaDecisionWorkflowId
   end: true
 ```
 
@@ -1305,7 +1305,7 @@ states:
 </tr>
 </table>
 
-### Send CloudEvent On Workfow Completion Example
+### Send CloudEvent On Workflow Completion Example
 
 #### Description
 

schema/workflow.json

@@ -56,7 +56,7 @@
             "failOnValidationErrors": {
               "type": "boolean",
               "default": true,
-              "description": "Determines if workfow execution should continue if there are validation errors"
+              "description": "Determines if workflow execution should continue if there are validation errors"
             }
           },
           "additionalProperties": false,

specification.md

@@ -3,7 +3,7 @@
 ## Abstract
 
 A specification that defines a vendor-neutral and declarative workflow language,
-targeting the serverless computing technology domain.
+targeting the Serverless computing technology domain.
 
 ## Status of this document
 
@@ -106,7 +106,7 @@ This section describes some of the core Serverless Workflow concepts:
 
 ### Workflow Definition
 
-A workflow definition is a single artefact written in the Serverless Workflow 
+A workflow definition is a single artifact written in the Serverless Workflow 
 language. It consists of the core [Workflow Definition Structure](#Workflow-Definition-Structure) 
 and the [Workflow Model](#Workflow-Model) It defines a blueprint used by runtimes for its execution. 
 
@@ -164,7 +164,7 @@ logic, so does the workflow data:
 <img src="media/spec/workflowdataflow.png" height="400" alt="Serverless Workflow Data Flow"/>
 </p>
 
-The initial [Workfow data input](#Workflow-data-input) is passed to the workflow starting state as its data input.
+The initial [Workflow data input](#Workflow-data-input) is passed to the workflow starting state as its data input.
 When a state finishes its execution, [its data output is passed as data input to the next state](#Information-passing-Between-States) that should be executed.
 
 When workflow execution ends, the last executed workflow state's data output becomes the final [Workflow data output](#Workflow-data-output).
@@ -1023,7 +1023,7 @@ gRPC uses [Protocol Buffers](https://developers.google.com/protocol-buffers/docs
 and the methods on those services that can be invoked. 
 
 Let's look at an example of invoking a service method using RPC. For this example let's say we have the following
-gRP protocol buffer definition in a myuserservice.proto file:
+gRPC protocol buffer definition in a myuserservice.proto file:
 
 ```text
 service UserService {