Format markdown (#1123)

* Format markdown

Produced via: `prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)`

* Revert bad diff

Author: mattmoor-sockpuppet

contributing/WORKING-GROUPS.md

@@ -68,14 +68,14 @@ API
 
 [Build](https://github.com/knative/build), Builders, and Build templates
 
-| Artifact                   | Link                                                                                                                                                                                                                             |
-| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Forum                      | [knative-dev@](https://groups.google.com/forum/#!forum/knative-dev)                                                                                                                                                              |
-| Community Meeting VC       | [meet.google.com/hau-nwak-tgm](https://meet.google.com/hau-nwak-tgm) <br>Or dial in:<br>(US) +1 219-778-6103‬ PIN: ‪573 000‬#                                                                                                    |
+| Artifact                   | Link                                                                                                                                                                                                                                        |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Forum                      | [knative-dev@](https://groups.google.com/forum/#!forum/knative-dev)                                                                                                                                                                         |
+| Community Meeting VC       | [meet.google.com/hau-nwak-tgm](https://meet.google.com/hau-nwak-tgm) <br>Or dial in:<br>(US) +1 219-778-6103‬ PIN: ‪573 000‬#                                                                                                               |
 | Community Meeting Calendar | Every other Wednesday 10:00a-10:30a PST <br>[Calendar](https://calendar.google.com/event?action=TEMPLATE&tmeid=MTBkb3MwYnVrbDd0djE0a2kzcmpmbjZndm9fMjAxODA5MTJUMTcwMDAwWiBqYXNvbmhhbGxAZ29vZ2xlLmNvbQ&tmsrc=jasonhall%40google.com&scp=ALL) |
-| Meeting Notes              | [Notes](https://docs.google.com/document/d/1e7gMVFlJfkFdTcaWj2qETeRD9kSBG2Vh8mASPmQMYC0/edit)                                                                                                                                    |
-| Document Folder            | [Folder](https://drive.google.com/corp/drive/folders/1ov16HvPam-v_FXAGEaUdHok6_hUAoIoe)                                                                                                                                          |
-| Slack Channel              | [#build-crd](https://knative.slack.com/messages/build-crd)                                                                                                                                                                       |
+| Meeting Notes              | [Notes](https://docs.google.com/document/d/1e7gMVFlJfkFdTcaWj2qETeRD9kSBG2Vh8mASPmQMYC0/edit)                                                                                                                                               |
+| Document Folder            | [Folder](https://drive.google.com/corp/drive/folders/1ov16HvPam-v_FXAGEaUdHok6_hUAoIoe)                                                                                                                                                     |
+| Slack Channel              | [#build-crd](https://knative.slack.com/messages/build-crd)                                                                                                                                                                                  |
 
 | &nbsp;                                                   | Leads      | Company | Profile                                 |
 | -------------------------------------------------------- | ---------- | ------- | --------------------------------------- |

docs/build/auth.md

@@ -209,14 +209,12 @@ credentials are then used to authenticate with the Docker registry.
 ## Kubernetes's Docker registry's secret
 
 Kubernetes defines two types of secrets for Docker registries :
-`kubernetes.io/dockercfg` and
-`kubernetes.io/dockerconfigjson`. Knative supports those secrets in
-addition to the one described above.
-
-1. Define a `Secret` from a Docker client configuration file, as
-   documented in [Pull an Image from a Private
-   Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) 
-   
+`kubernetes.io/dockercfg` and `kubernetes.io/dockerconfigjson`. Knative supports
+those secrets in addition to the one described above.
+
+1. Define a `Secret` from a Docker client configuration file, as documented in
+   [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/)
+
    ```bash
    kubectl create secret generic regcred \
     --from-file=.dockerconfigjson=<path/to/.docker/config.json> \
@@ -225,42 +223,42 @@ addition to the one described above.
 
 1. Direct a `ServiceAccount` to use this `Secret`:
 
-	```yaml
-    apiVersion: v1
-    kind: ServiceAccount
-    metadata:
-      name: build-bot
-    secrets:
-      - name: regcred
-	```
-
-1.  Use that `ServiceAccount` in your `Build`:
+   ```yaml
+   apiVersion: v1
+   kind: ServiceAccount
+   metadata:
+     name: build-bot
+   secrets:
+     - name: regcred
+   ```
 
-    ```yaml
-    apiVersion: build.knative.dev/v1alpha1
-    kind: Build
-    metadata:
-      name: build-with-basic-auth
-    spec:
-      serviceAccountName: build-bot
-      steps:
-      ...
-    ```
+1. Use that `ServiceAccount` in your `Build`:
+
+   ```yaml
+   apiVersion: build.knative.dev/v1alpha1
+   kind: Build
+   metadata:
+     name: build-with-basic-auth
+   spec:
+     serviceAccountName: build-bot
+     steps:
+     ...
+   ```
 
-1.  Execute the build:
+1. Execute the build:
 
-    ```shell
-    kubectl apply --filename secret.yaml --filename serviceaccount.yaml --filename build.yaml
-    ```
+   ```shell
+   kubectl apply --filename secret.yaml --filename serviceaccount.yaml --filename build.yaml
+   ```
 
 When this build executes, before steps execute, a `~/.docker/config.json` will
 be generated containing the credentials configured in the `Secret`, and these
 credentials are then used to authenticate with the Docker registry.
 
-If both `kubernetes.io/*` and knative flavored basic authentication
-secret are provided, knative will merge the credentials from those
-two ; knative flavored credentials taking precendence over
-`kubernetes.io/dockerconfigjson` (or `kubernetes.io/dockercfg`) ones.
+If both `kubernetes.io/*` and knative flavored basic authentication secret are
+provided, knative will merge the credentials from those two ; knative flavored
+credentials taking precendence over `kubernetes.io/dockerconfigjson` (or
+`kubernetes.io/dockercfg`) ones.
 
 ### Guiding credential selection
 

docs/eventing/README.md

@@ -258,33 +258,49 @@ See the [Cronjob Source](samples/cronjob-source) example.
 
 ### KafkaSource
 
-The KafkaSource reads events from an Apache Kafka Cluster, and passes these to a Knative Serving application so that they can be consumed.
+The KafkaSource reads events from an Apache Kafka Cluster, and passes these to a
+Knative Serving application so that they can be consumed.
 
 **Spec fields**:
 
 - `consumerGroup`: `string` Name of a Kafka consumer group.
-- `bootstrapServers`: `string` Comma separated list of `hostname:port` pairs for the Kafka Broker.
+- `bootstrapServers`: `string` Comma separated list of `hostname:port` pairs for
+  the Kafka Broker.
 - `topics`: `string` Name of the Kafka topic to consume messages from.
 
-See the [Kafka Source](https://github.com/knative/eventing-sources/tree/master/contrib/kafka/samples) example.
+See the
+[Kafka Source](https://github.com/knative/eventing-sources/tree/master/contrib/kafka/samples)
+example.
 
 ### CamelSource
 
-A CamelSource is an event source that can represent any existing [Apache Camel component](https://github.com/apache/camel/tree/master/components) that provides a consumer side, and enables publishing events to an addressable endpoint. Each Camel endpoint has the form of a URI where the scheme is the ID of the component to use.
+A CamelSource is an event source that can represent any existing
+[Apache Camel component](https://github.com/apache/camel/tree/master/components)
+that provides a consumer side, and enables publishing events to an addressable
+endpoint. Each Camel endpoint has the form of a URI where the scheme is the ID
+of the component to use.
 
-CamelSource requires [Camel-K](https://github.com/apache/camel-k#installation) to be installed into the current namespace.
+CamelSource requires [Camel-K](https://github.com/apache/camel-k#installation)
+to be installed into the current namespace.
 
 **Spec fields**:
 
 - source: information on the kind of Camel source that should be created.
-  - component: the default kind of source, enables creating an EventSource by configuring a single Camel component.
-    - uri: `string` contains the Camel URI that should be used to push events into the target sink.
-    - properties: `key/value map` contains Camel global options or component specific configuration. Options are available in the documentation of each existing Apache Camel component.
-- serviceAccountName: `string` an optional service account that can be used to run the source pod.
-- image: `string` an optional base image to use for the source pod, mainly for development purposes.
-
-See the [CamelSource](https://github.com/knative/eventing-sources/blob/master/contrib/camel/samples/README.md) example.
-
+  - component: the default kind of source, enables creating an EventSource by
+    configuring a single Camel component.
+    - uri: `string` contains the Camel URI that should be used to push events
+      into the target sink.
+    - properties: `key/value map` contains Camel global options or component
+      specific configuration. Options are available in the documentation of each
+      existing Apache Camel component.
+- serviceAccountName: `string` an optional service account that can be used to
+  run the source pod.
+- image: `string` an optional base image to use for the source pod, mainly for
+  development purposes.
+
+See the
+[CamelSource](https://github.com/knative/eventing-sources/blob/master/contrib/camel/samples/README.md)
+example.
 
 ## Getting Started
 

docs/eventing/samples/cronjob-source/README.md

@@ -96,6 +96,7 @@ kail -l serving.knative.dev/service=message-dumper -c user-container --since=10m
 ### Cleanup
 
 You can remove the Cron Event Source via:
+
 ```shell
 kubectl delete --filename cronjob-source.yaml
 ```

docs/eventing/samples/iot-core/README.md

@@ -204,19 +204,22 @@ see them in the subscriber.
 To cleanup the knative resources:
 
 1.  Remove the gcppubsub controller:
+
     ```shell
     pushd $HOME/go/src/github.com/knative/eventing-sources
     kubectl delete --filename config/default-gcppubsub.yaml
     popd
     ```
 
 2.  Remove the channel:
+
     ```shell
     sed "s/CHANNEL_NAME/$CHANNEL_NAME/" channel.yaml |
     kubectl --namespace default delete --filename -
     ```
 
 3.  Remove the gcppubsub source:
+
     ```shell
     sed -e "s/MY_GCP_PROJECT/$IOTCORE_PROJECT/" \
         -e "s/TOPIC_NAME/$IOTCORE_TOPIC_DATA/" \

docs/eventing/samples/kubernetes-event-source/README.md

@@ -95,7 +95,9 @@ Ce-Source: /apis/v1/namespaces/default/pods/busybox
 
 ### Cleanup
 
-You can remove the `Channel`, `Service Account`, `Event Sources`, and `Subscriber` via:
+You can remove the `Channel`, `Service Account`, `Event Sources`, and
+`Subscriber` via:
+
 ```shell
 kubectl --namespace default delete --filename channel.yaml
 kubectl --namespace default delete --filename serviceaccount.yaml