Fix typos and grammar (#408)

Author: yuandrew

README.md

@@ -41,7 +41,7 @@ Workflow Definition and an Activity Definition using API Key to authenticate wit
   server API. Additional
   documentation: [How to complete an Activity Execution asynchronously in Go](https://docs.temporal.io/application-development/foundations/#develop-activities)
 
-- [**Retry Activity Execution**](./retryactivity): This samples
+- [**Retry Activity Execution**](./retryactivity): This sample
   executes an unreliable Activity. The Activity is executed with a custom Retry Policy. If the Activity Execution fails,
   the Server will schedule a retry based on the Retry Policy. This Activity also includes a Heartbeat, which enables it
   to resume from the Activity Execution's last reported progress when it retries.
@@ -51,13 +51,13 @@ Workflow Definition and an Activity Definition using API Key to authenticate wit
   Workflow Execution after completing its last Run.
 
 - [**Child Workflow with ContinueAsNew**](./child-workflow-continue-as-new): Demonstrates
-  that the call to Continue-As-New, by a Child Workflow Execution, is *not visible to the a parent*. The Parent Workflow
+  that the call to Continue-As-New, by a Child Workflow Execution, is *not visible to the parent*. The Parent Workflow
   Execution receives a notification only when a Child Workflow Execution completes, fails or times out. This is a useful
   feature when there is a need to **process a large set of data**. The child can iterate over the data set calling
   Continue-As-New periodically without polluting the parents' history.
 
 - [**Cancellation**](./cancellation): Demonstrates how to cancel a
-  Workflow Execution by calling `CancelWorkflow`, an how to defer an Activity Execution that "cleans up" after the
+  Workflow Execution by calling `CancelWorkflow`, and how to defer an Activity Execution that "cleans up" after the
   Workflow Execution has been cancelled.
 
 - **Coroutines**: Do not use native `go` routines in Workflows. Instead use Temporal coroutines (`workflow.Go()`) to
@@ -68,7 +68,7 @@ Workflow Definition and an Activity Definition using API Key to authenticate wit
   , [PSO](./pso) Workflow examples.
 
 - [**Cron Workflow**](./cron): Demonstrates a recurring Workflow
-  Execution that occurs according to a cron schedule. This samples showcases the `HasLastCompletionResult`
+  Execution that occurs according to a cron schedule. This sample showcases the `HasLastCompletionResult`
   and `GetLastCompletionResult` APIs which are used to pass information between executions. Additional
   documentation: [What is a Temporal Cron Job?](https://docs.temporal.io/docs/content/what-is-a-temporal-cron-job).
 
@@ -176,11 +176,11 @@ These samples demonstrate some common control flow patterns using Temporal's Go
   not finished.
 
 - [**Split/Merge Future**](./splitmerge-future): Demonstrates how to
-  use futures to await for completion of multiple activities invoked in parallel. This samples to processes chunks of a
+  use futures to await completion of multiple activities invoked in parallel. This sample processes chunks of a
   large work item in parallel, and then merges the intermediate results to generate the final result.
 
 - [**Split/Merge Selector**](./splitmerge-selector): Demonstrates how
-  to use Selector to process activity results as soon as they become available. This samples to processes chunks of a
+  to use Selector to process activity results as soon as they become available. This sample processes chunks of a
   large work item in parallel, and then merges the intermediate results to generate the final result.
 
 - [**Synchronous Proxy Workflow pattern**](./synchronous-proxy): This
@@ -198,7 +198,7 @@ These samples demonstrate some common control flow patterns using Temporal's Go
 
 - [**Nexus**](./nexus): Demonstrates how to use the Nexus APIs to facilitate cross namespace calls.
 - [**Nexus Cancelation**](./nexus-cancelation): Demonstrates how to cancel a Nexus operation from a caller workflow.
-- [**Nexus Context Propagation**](./nexus-context-propagation): Demonstrates how to propgate context through client calls, workflows, and Nexus headers.
+- [**Nexus Context Propagation**](./nexus-context-propagation): Demonstrates how to propagate context through client calls, workflows, and Nexus headers.
 
 ### Scenario based examples
 
@@ -213,7 +213,7 @@ These samples demonstrate some common control flow patterns using Temporal's Go
 
 - [**File Processing**](./fileprocessing): Demonstrates how to
   download and process a file using set of Activities that run on the same host. Activities are executed to download a
-  file from the web, store it locally on the host, and then "process it". This samples showcases how to handle a
+  file from the web, store it locally on the host, and then "process it". This sample showcases how to handle a
   scenario where all subsequent Activities need to execute on the same host as the first Activity in the sequence. In
   Go, this is achieved by using the Session APIs.
 
@@ -222,8 +222,8 @@ These samples demonstrate some common control flow patterns using Temporal's Go
   use of parallel executions, `ContinueAsNew` for long histories, a Query API, and the use of a custom `DataConverter`
   for serialization.
 
-- [**Polling Services**](./polling): Recommended implementation of an activity that needs to periodically poll an external 
-resource waiting its successful completion
+- [**Polling Services**](./polling): Recommended implementation of an activity that needs to periodically poll an external
+resource waiting for its successful completion
 
 - [**Prometheus Metrics**](./metrics): Demonstrates how to instrument
   Temporal with Prometheus and Uber's Tally library.
@@ -235,7 +235,7 @@ resource waiting its successful completion
   Demonstrates how to accept requests via signals and use queries to poll for responses.
 
 - [**Request/Response with Response Updates**](./reqrespupdate):
-  Demonstrates how to accept requests and responsond via updates.
+  Demonstrates how to accept requests and respond via updates.
 
 - [**Early-Return**](./early-return):
   Demonstrates how to receive a response mid-workflow, while the workflow continues to run to completion.

nexus-cancelation/README.md

@@ -2,7 +2,7 @@
 
 This sample shows how to cancel a Nexus operation from a caller workflow.
 
-From more details on Nexus and how to setup to run this sample please see the [Nexus Sample](../nexus/README.md).
+For more details on Nexus and how to set up to run this sample, please see the [Nexus Sample](../nexus/README.md).
 
 ### Running the sample
 

nexus-cancelation/caller/workflows.go

@@ -64,7 +64,7 @@ func HelloCallerWorkflow(ctx workflow.Context, name string) (string, error) {
 		})
 	}
 	// Wait for all operations to resolve. Once the workflow completes, the server will stop trying to cancel any
-	// operations that have not yet recieved cancelation, letting them run to completion. It is totally valid to
+	// operations that have not yet received cancelation, letting them run to completion. It is totally valid to
 	// abandon operations for certain use cases.
 	wg.Wait(ctx)
 

nexus-context-propagation/README.md

@@ -2,7 +2,7 @@
 
 This sample shows how to propagate context through client calls, workflows, and Nexus headers.
 
-From more details on Nexus and how to setup to run this samples please see the [Nexus Sample](../nexus/README.md).
+For more details on Nexus and how to set up to run this sample, please see the [Nexus Sample](../nexus/README.md).
 
 ### Running the sample