Fix TYPOs

Fix TYPOs using `misspell` suggestions.

Signed-off-by: Matthias Diester <[email protected]>

Author: HeavyWombat

README.md

@@ -2,7 +2,7 @@
 
 # Tutorials and Samples for IBM Cloud Code Engine
 
-This respository is split into two types of educational material: Tutorials
+This repository is split into two types of educational material: Tutorials
 and Samples.
 
 Tutorials are meant to be complete end-to-end scenarios designed

bash/README.md

@@ -3,12 +3,12 @@
 This sample will show how to create an application that is nothing more than
 a bash script. While there is still an HTTP server as part of the solution,
 you should be able to reuse the `bash` container image in other projects
-without neeeding to do more than just provide a custom bash script.
+without needing to do more than just provide a custom bash script.
 
 In this setup the follow will happen:
 - during the startup of each instance of your applciation, if present,
   a file named `/app/init` will be invoked. You can also set an environment
-  variabled called `INIT` to the path of an additional program that you
+  variable called `INIT` to the path of an additional program that you
   want executed. The environment variable program will be called after
   `/app/init`. This allows for you to execute code that you want only
   run once per instance - and not on each incoming HTTP request.

cos2cos/README.md

@@ -5,7 +5,7 @@ demonstrates a simple event-driven application pattern wherein the uploading of
 an object to a Cloud Object Storage (COS) bucket generates an event.  When the
 app receives the event, it parses out the bucket and object key from the event,
 downloads the object (file), "processes" it, and then uploads the resulting
-file to a separate (preconfigured) destination bucket.  The app then deletes
+file to a separate (pre-configured) destination bucket.  The app then deletes
 the file from the original source bucket.
 
 The app also includes a listener for cron events.  Upon receipt of a cron event,

daemonjob/README.md

@@ -13,7 +13,7 @@ The code will also print the list of environment variables to the log file
 for debugging purposes.
 
 The sample script will also submit the job twice. First by creating a
-job defintion, followed by submitting it, and then it will submit a new
+job definition, followed by submitting it, and then it will submit a new
 job directly without first creating a job definition. In the second case
 it will also change the message printed via the `MSG` environment variable.
 

fruit-counter/README.md

@@ -1,5 +1,5 @@
 # Fruit Counter
 
-Combine IBM Cloudant and IBM Code Engine to deploy a scalable and higly available web app. [Follow the tutorial here](https://www.ibm.com/cloud/blog/ibm-code-engine-and-ibm-cloudant-serverless-data-and-infrastructure).
+Combine IBM Cloudant and IBM Code Engine to deploy a scalable and highly available web app. [Follow the tutorial here](https://www.ibm.com/cloud/blog/ibm-code-engine-and-ibm-cloudant-serverless-data-and-infrastructure).
 
 

github/github.go

@@ -88,7 +88,7 @@ func ProcessEvent(eventType string, eventBody []byte) {
 		return
 	}
 
-	log.Printf("%s commited %q to %q branch",
+	log.Printf("%s committed %q to %q branch",
 		PushEvent.Pusher.Name, PushEvent.After, PushEvent.Ref)
 
 	// Now we'd normally do a build, but let's just fake it.

job/README.md

@@ -1,7 +1,7 @@
 # Job
 
 This sample shows up to run a batch job. It will create the batch job two ways:
-1 - first, it'll create a Job definition (the config informatin about a job)
+1 - first, it'll create a Job definition (the config information about a job)
     and then it submits that Job to actually do the work.
 2 - second, it'll submit the Job directly without creating the definition
     first. Both will generate the same results though.

kafka/README.md

@@ -10,7 +10,7 @@ that to setup our subscription and Kafka "sender" application that will
 add messages to our Kafka instance.
 
 The second part of the sample will create a Kafka subscription and send
-all incoming messags to a new application called "receiver". In order
+all incoming messages to a new application called "receiver". In order
 to setup the Kafka subscription we'll first need to store the credentials
 (`username` and `password`) in a secret, then pass in that secret name on
 the subscription "create" command. We'll also need to pass in the list of

testjob/README.md

@@ -16,7 +16,7 @@ The code will also print the list of environment variables to the log file
 for debugging purposes.
 
 The sample script will also submit the job twice. First by creating a
-job defintion, followed by submitting it, and then it will submit a new
+job definition, followed by submitting it, and then it will submit a new
 job directly without first creating a job definition. In the second case
 it will also change the message printed via the `MSG` environment variable.
 

websocket/README.md

@@ -3,7 +3,7 @@
 This sample will show how to use WebSockets to talk to a Code Engine
 Application.  The sample itself is fairly straight forward. It starts a server
 that will upgrade any incoming HTTP request into a WebSocket connection. The
-client initates a request (which, under the covers, converts the
+client initiates a request (which, under the covers, converts the
 HTTP request into a WebSocket). The client will then send a series of
 messages (strings) and in parallel reads messages from the server. The
 server will simply reverse the characters in the strings to generate the