Merge pull request #40 from triggermesh/fix-typos

fix typos in docs

Author: Sameer Naik

docs/guides/actions.md

@@ -6,7 +6,7 @@ TriggerMesh Actions are based on [Tekton Pipeline](https://github.com/tektoncd/p
 
   You can express a _Task_ in a manifest. For example, the following manifest represents a Task that will echo _Hello World_:
 
-```
+```yaml
 apiVersion: tekton.dev/v1alpha1
 kind: Task
 metadata:
@@ -19,7 +19,7 @@ spec:
         - echo
       args:
         - "hello world"
-``` 
+```
 
 The TM console provides an easy to use YAML window for deploying Tasks from the browser. This is accessed by selecting _Tasks_ from the Navigation menu.
 
@@ -29,8 +29,8 @@ The TM console provides an easy to use YAML window for deploying Tasks from the
   Click on the _Create Task_ button and select _from YAML_, to create a new task.
 
  ![](../images/tmDashCreateTask.png)
-  
-  
+
+
 You will be presented with the following view in which you can paste your Task manifest.
 
 ![](../images/tmTaskYaml.png)
@@ -50,4 +50,4 @@ Clicking on the object name will lead you to the _Task Run Details_ here we can
 ![](../images/taskrunlogs.png)
 
 
-### CLI lovers can use use [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) and [`tm`](https://github.com/triggermesh/tm) to [create Tasks from the CLI.](https://github.com/triggermesh/tm#deployment-pipelines)
+### CLI lovers can use use [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) and [`tm`](https://github.com/triggermesh/tm) to [create Tasks from the CLI.](https://github.com/triggermesh/tm#deployment-pipelines)

docs/guides/cd.md

@@ -2,14 +2,14 @@
 
 
 
-The Triggermesh console provides an interface called [Repositories.](https://cloud.triggermesh.io/function-triggers) Here the user is able to select a codebase, from a linked repository provider, to be continuously deployed. This codebase **must** contain a deployment manifest[^1] . 
+The Triggermesh console provides an interface called [Repositories.](https://cloud.triggermesh.io/function-triggers) Here the user is able to select a codebase, from a linked repository provider, to be continuously deployed. This codebase **must** contain a deployment manifest[^1] .
 
 
 ## Register the repository
 
-###### The following example uses this [sample repository.](https://github.com/sebgoa/tmserverless) To follow along begin by forking the example to your repository provider. 
+###### The following example uses this [sample repository.](https://github.com/sebgoa/tmserverless) To follow along begin by forking the example to your repository provider.
 
-1. Select the _Repositories_ section from the Navigation menu and then _CREATE NEW_ 
+1. Select the _Repositories_ section from the Navigation menu and then _CREATE NEW_
 
 ![](../images/tmRepoView.png)
 
@@ -22,7 +22,7 @@ The Triggermesh console provides an interface called [Repositories.](https://clo
 
 ![](../images/repowiz2.png)
 
-4. Here you can specify the location of the `serverless.yaml` manifest as well as select specific _Branch_ and _Tag_ name's from the repository. 
+4. Here you can specify the location of the `serverless.yaml` manifest as well as select specific _Branch_ and _Tag_ name's from the repository.
 
 ![](../images/repowiz3.png)
 
@@ -32,7 +32,7 @@ The Triggermesh console provides an interface called [Repositories.](https://clo
 
 ## Viewing The Deployment
 
-***After every sucessful registration of a new repository a _Task_ will be created for it.***
+***After every successful registration of a new repository a _Task_ will be created for it.***
 
 * Navigate to the _Tasks_ view in the **Actions** section and click on the _Task_ name.
 
@@ -61,4 +61,4 @@ The Triggermesh console provides an interface called [Repositories.](https://clo
 ![](../images/serviceview.png)
 
 
-[^1]: A sample manifest can be found here -> https://github.com/sebgoa/transform/blob/master/serverless.yaml
+[^1]: A sample manifest can be found here -> [https://github.com/sebgoa/transform/blob/master/serverless.yaml](https://github.com/sebgoa/transform/blob/master/serverless.yaml)

docs/guides/gettingstarted.md

@@ -38,8 +38,8 @@ If you know the Knative API already you can choose to paste the Service YAML man
 
 For example, given this manifest:
 
-```
-apiVersion: serving.knative.dev/v1alpha1
+```yaml
+apiVersion: serving.knative.dev/v1
 kind: Service
 metadata:
     name: hello

docs/guides/secrets.md

@@ -2,20 +2,17 @@
 
 The TriggerMesh console provides a central location to view and store sensitive information called `Secrets.` The secrets created here can then be used by any service deployed via the Triggermesh platform.
 
-In the top right, after selecting the `Secrets` section from the sidebar, you will se a button labled `+ ADD SECRET.` Selecting the button here will give you a choice to create various secrets (e.g AWS, GitHub, GitLab, GCP)
-
+In the top right, after selecting the `Secrets` section from the sidebar, you will see a button labeled `+ ADD SECRET.` Selecting the button here will give you a choice to create various secrets (e.g AWS, GitHub, GitLab, GCP)
 
 ![](../images/addsecretview.png)
 
-
-
 ## Generic Secrets
 
 If you need a generic secret you can also create it. The wizard will walk you through adding as many keys and values as you need.
 
 ![](../images/genericsecret.png)
 
-## AWS API keys 
+## AWS API keys
 
 All the AWS event sources need access to some AWS API credentials to be able to establish a secure connection.
 
@@ -47,4 +44,4 @@ You can interact with your secrets using [`kubectl`](https://kubernetes.io/docs/
 
 ```
 kubectl --kubeconfig=config.json -n <your_login_username> get secrets
-```
+```