From 7ac57addecb2b5a9de94bbc0a93ad0eb0eaaad6c Mon Sep 17 00:00:00 2001
From: "Matt Moore (via sockpuppet)" <mattmoor+sockpuppet@google.com>
Date: Sun, 14 Apr 2019 18:44:46 +0000
Subject: [PATCH] Format markdown

Produced via: `prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)`
---
 docs/broker/README.md | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)

diff --git a/docs/broker/README.md b/docs/broker/README.md
index b0dc6be9ee4..335e132b21f 100644
--- a/docs/broker/README.md
+++ b/docs/broker/README.md
@@ -53,24 +53,38 @@ spec:
 
 ### ClusterChannelProvisioner
 
-`Broker`'s use their `spec.channelTemplate` to create their internal `Channel`s, which dictate the durability guarantees of events sent to that `Broker`. If `spec.channelTemplate` is not specified, then the [default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/) for their namespace is used.
+`Broker`'s use their `spec.channelTemplate` to create their internal `Channel`s,
+which dictate the durability guarantees of events sent to that `Broker`. If
+`spec.channelTemplate` is not specified, then the
+[default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/)
+for their namespace is used.
 
 #### Setup
 
-Have a `ClusterChannelProvisioner` installed and set as the [default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/) for the namespace you are interested in. For development, the [`in-memory` `ClusterChannelProvisioner`](https://github.com/knative/eventing/tree/master/config/provisioners/in-memory-channel#deployment-steps) is normally used.
+Have a `ClusterChannelProvisioner` installed and set as the
+[default provisioner](https://www.knative.dev/docs/eventing/channels/default-channels/)
+for the namespace you are interested in. For development, the
+[`in-memory` `ClusterChannelProvisioner`](https://github.com/knative/eventing/tree/master/config/provisioners/in-memory-channel#deployment-steps)
+is normally used.
 
 #### Changing
 
-**Note** changing the `ClusterChannelProvisioner` of a running `Broker` will lose all in-flight events.
+**Note** changing the `ClusterChannelProvisioner` of a running `Broker` will
+lose all in-flight events.
 
-If you want to change which `ClusterChannelProvisioner` is used by a given `Broker`, then determine if the `spec.channelTemplate` is specified or not.
+If you want to change which `ClusterChannelProvisioner` is used by a given
+`Broker`, then determine if the `spec.channelTemplate` is specified or not.
 
 If `spec.channelTemplate` is specified:
+
 1. Delete the `Broker`.
 1. Create the `Broker` with the updated `spec.channelTemplate`.
 
 If `spec.channelTemplate` is not specified:
-1. Change the [default provisioner](https://github.com/knative/docs/blob/master/docs/eventing/channels/default-channels.md#setting-the-default-channel-configuration) for the namespace that `Broker` is in.
+
+1. Change the
+   [default provisioner](https://github.com/knative/docs/blob/master/docs/eventing/channels/default-channels.md#setting-the-default-channel-configuration)
+   for the namespace that `Broker` is in.
 1. Delete and recreate the `Broker`.
 
 ### Broker