Fix typos (#550)

* Fix typo

Activties -> Activities

* Fix typos

acvitivities -> activities

docs/content/labs/aws-iot.md

@@ -47,7 +47,7 @@ After that, click on "_Map to flow outputs_" to map the output parameters you cr
 
 ## Step 3: Add activities
 
-You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 3a](../../images/labs/aws-iot/step3a.png)
 

docs/content/labs/bookstore.md

@@ -47,7 +47,7 @@ Now for the outputs, click on "_Map to flow outputs_" to map the output paramete
 
 ## Step 3: Adding activities
 
-You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 3a](../../images/labs/bookstore/step3a.png)
 

docs/content/labs/helloworld.md

@@ -50,7 +50,7 @@ To create a new app, open the Flogo Web UI and from there, click "_New_" to crea
 
 In Flogo, a flow is an implementation of an action and is the primary tool to implement business logic. A flow can consist of a number of different constructs:
 
-* **Activties**: One or more activities that implement specific logic (for example write to a database, invoke a REST endpoint, etc)
+* **Activities**: One or more activities that implement specific logic (for example write to a database, invoke a REST endpoint, etc)
 * **Links**: Each activity is connected via a link (_Links can contain conditional logic to alter the path of a flow_)
 
 Flows, as previously stated in the triggers section, can exist without a trigger. Thus, flows operate very similar to functions, that is, a single flow can define its own input & output parameters. Thus, enabling a flow to be reused regardless of the trigger entrypoint To create a new flow you can click either the `+ New Flow` button at the top or the `Create a flow` button in the middle of the screen.
@@ -102,7 +102,7 @@ The URL on which our microservice will listen will be `http://localhost:9233/tes
 
 ## Step 5: Adding activities
 
-An activity is the unit of work that can be leveraged within a Flow. An activity can be any number of things and can be compared to a simple function in Go or any other procedural language, that is, an activity accepts input params and will return one or more objects on return, both input & output params are defined by the activity metadata. You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+An activity is the unit of work that can be leveraged within a Flow. An activity can be any number of things and can be compared to a simple function in Go or any other procedural language, that is, an activity accepts input params and will return one or more objects on return, both input & output params are defined by the activity metadata. You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 5](../../images/labs/helloworld/step5.png)
 
@@ -126,4 +126,4 @@ Project Flogo can build binaries for most platforms that exist. If you choose to
 
 ## Step 8: Run your app
 
-To run the app double-click it (on Windows), or open a terminal and execute the downloaded binary. As you'll do that, you'll not only see the output of the log step, but you'll see the same in your browser window as well. The URL on which our microservice will listen should be `http://localhost:9233/test/:name` (or might be different if you made changes in the previous steps). If you're running it on your machine you can open a browser window and go to `http://localhost:9233/test/flogo` to see what the output was (spoiler alert: you'll see `"Hello flogo"` in your web browser). To stop your app simply close the terminal window in which you started the app or press **ctrl + c**
+To run the app double-click it (on Windows), or open a terminal and execute the downloaded binary. As you'll do that, you'll not only see the output of the log step, but you'll see the same in your browser window as well. The URL on which our microservice will listen should be `http://localhost:9233/test/:name` (or might be different if you made changes in the previous steps). If you're running it on your machine you can open a browser window and go to `http://localhost:9233/test/flogo` to see what the output was (spoiler alert: you'll see `"Hello flogo"` in your web browser). To stop your app simply close the terminal window in which you started the app or press **ctrl + c**

docs/content/labs/invoiceservice.md

@@ -62,7 +62,7 @@ The URL on which our microservice will listen will be `http://localhost:9234/api
 
 ## Step 3: Add activities
 
-You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 3a](../../images/labs/invoiceservice/step3a.png)
 

docs/content/labs/paymentservice.md

@@ -62,7 +62,7 @@ The URL on which our microservice will listen will be `http://localhost:9233/api
 
 ## Step 3: Add activities
 
-You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 3a](../../images/labs/paymentservice/step3a.png)
 

docs/content/labs/pubnub.md

@@ -49,7 +49,7 @@ After that, click on "_Map to flow inputs_" to map the message from PubNub to th
 
 ## Step 5: Adding activities
 
-You’ll have to add some acvitivities to the flow for it to do something. In this demo you'll add two activities to the flow. The first activity will log the message and the second one will store the data in a file. To add an activity click on the other large `+` sign
+You’ll have to add some activities to the flow for it to do something. In this demo you'll add two activities to the flow. The first activity will log the message and the second one will store the data in a file. To add an activity click on the other large `+` sign
 
 ![step 5](../../images/labs/pubnub/step5.png)
 

docs/content/labs/raspberry-iot.md

@@ -47,7 +47,7 @@ After that, click on "_Map to flow outputs_" to map the output parameters you cr
 
 ## Step 3: Add activities
 
-You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the other large `+` sign
+You’ll have to add some activities to the flow for it to do something. To add an activity click on the other large `+` sign
 
 ![step 3a](../../images/labs/raspberry-iot/step3a.png)
 

docs/content/labs/timers.md

@@ -36,7 +36,7 @@ Click "_save_" to make sure everything is, well…, saved. You can click the lit
 
 ## Step 3: Add activities
 
-An activity is the unit of work that can be leveraged within a Flow. An activity can be any number of things and can be compared to a simple function in Go or any other procedural language, that is, an activity accepts input params and will return one or more objects on return, both input & output params are defined by the activity metadata. You’ll have to add some acvitivities to the flow for it to do something. To add an activity click on the large `+` sign
+An activity is the unit of work that can be leveraged within a Flow. An activity can be any number of things and can be compared to a simple function in Go or any other procedural language, that is, an activity accepts input params and will return one or more objects on return, both input & output params are defined by the activity metadata. You’ll have to add some activities to the flow for it to do something. To add an activity click on the large `+` sign
 
 ![step 3a](../../images/labs/timers/step3a.png)