Correct rendering of bash instructions

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>

Author: matzew

docs/eventing/sinks/integration-sink/aws_s3.md

@@ -6,9 +6,9 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) S3 service, through
 
 For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS S3 Sink Example
 

docs/eventing/sinks/integration-sink/aws_sns.md

@@ -6,9 +6,9 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Notification
 
 For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS SNS Sink Example
 

docs/eventing/sinks/integration-sink/aws_sqs.md

@@ -6,9 +6,9 @@ The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Queue Servic
 
 For connecting to AWS the `IntegrationSink` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS SQS Sink Example
 

docs/eventing/sources/integration-source/aws_ddbstreams.md

@@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) DynamoDB Streams
 
 For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS DynamoDB Streams Example
 

docs/eventing/sources/integration-source/aws_s3.md

@@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) S3 service, throu
 
 For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS S3 Source Example
 

docs/eventing/sources/integration-source/aws_sqs.md

@@ -6,9 +6,9 @@ The `IntegrationSource` supports the Amazon Web Services (AWS) Simple Queue Serv
 
 For connecting to AWS the `IntegrationSource` uses Kubernetes `Secret`, present in the namespace of the resource. The `Secret` can be created like:
 
-    ```bash
-    kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
-    ```
+  ```bash
+  kubectl -n <namespace> create secret generic my-secret --from-literal=aws.accessKey=<accessKey> --from-literal=aws.secretKey=<secretKey>
+  ```
 
 ## AWS SQS Source Example