Update broker-developer-config-options.md

 The full example moved to end of the page

Author: pembebiri

docs/eventing/brokers/broker-developer-config-options.md

@@ -2,6 +2,27 @@
 
 ## Broker configuration 
 
+- You can specify any valid `name` for your broker. Using `default` will create a broker named `default`.
+- The `namespace` must be an existing namespace in your cluster. Using `default` will create the broker in the `default` namespace.
+
+###  Event Delivery Options
+- You can use `dead-letter sink`  for error handling and auditing of undelivered messages. Specify Kubernetes object reference where undelivered messages will be sent using `ref` and an optional URI to route undelivered messages using `uri`.
+- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be  `exponantial` or `linear`.
+- You can set the `Backoff delay ` to specify the initial delay before retrying, using the ISO 8601 duration format.
+- You can specify the number of retry attempts before sending the event to the dead-letter sink using the `retry` configuration.
+- `spec.delivery` is used to configure event delivery options. Event delivery options specify what happens to an event that fails to be delivered to an event sink. For more information, see the documentation on [Event delivery](../event-delivery.md).
+
+###  Advance broroker class options
+When a Broker is created without a specified `eventing.knative.dev/broker.class` annotation, the default `MTChannelBasedBroker` Broker class is used, as specified by default in the `config-br-defaults` ConfigMap. 
+
+In case you have multiple Broker classes installed in your cluster and want to use a non-default Broker class for a Broker, you can modify the `eventing.knative.dev/broker.class` annotation and `spec.config` for the Broker object.
+
+1. Set the `eventing.knative.dev/broker.class` annotation. Replace `MTChannelBasedBroker` in the following example with the class type you want to use. Be aware that the Broker class annoation is immutable and thus can't be updated after the Broker got created:
+
+2. Configure the `spec.config` with the details of the ConfigMap that defines the required configuration for the Broker class (e.g. with some Channel configurations in case of the `MTChannelBasedBroker`):
+
+For further information about configuring a default Broker class cluster wide or on a per namespace basis, check the [Administrator configuration options](../configuration/broker-configuration.md#configuring-the-broker-class).
+
 The following is a full example of a Channel based Broker object which shows the possible configuration options that you can modify:
 
 ```yaml
@@ -30,49 +51,3 @@ spec:
     backoffPolicy: exponential
     backoffDelay: "2007-03-01T13:00:00Z/P1Y2M10DT2H30M"
 ```
-- You can specify any valid `name` for your broker. Using `default` will create a broker named `default`.
-- The `namespace` must be an existing namespace in your cluster. Using `default` will create the broker in the `default` namespace.
-
-###  Event Delivery Options
-- You can use `dead-letter sink`  for error handling and auditing of undelivered messages. Specify Kubernetes object reference where undelivered messages will be sent using `ref` and an optional URI to route undelivered messages using `uri`.
-- You can set the `Backoff policies` to define the delay strategy between retry attempts. It can be  `exponantial` or `linear`.
-- You can set the `Backoff delay ` to specify the initial delay before retrying, using the ISO 8601 duration format.
-- You can specify the number of retry attempts before sending the event to the dead-letter sink using the `retry` configuration.
-- `spec.delivery` is used to configure event delivery options. Event delivery options specify what happens to an event that fails to be delivered to an event sink. For more information, see the documentation on [Event delivery](../event-delivery.md).
-
-###  Advance broroker class options
-When a Broker is created without a specified `eventing.knative.dev/broker.class` annotation, the default `MTChannelBasedBroker` Broker class is used, as specified by default in the `config-br-defaults` ConfigMap. 
-
-In case you have multiple Broker classes installed in your cluster and want to use a non-default Broker class for a Broker, you can modify the `eventing.knative.dev/broker.class` annotation and `spec.config` for the Broker object.
-
-1. Set the `eventing.knative.dev/broker.class` annotation. Replace `MTChannelBasedBroker` in the following example with the class type you want to use. Be aware that the Broker class annoation is immutable and thus can't be updated after the Broker got created:
-
-    ```yaml
-    apiVersion: eventing.knative.dev/v1
-    kind: Broker
-    metadata:
-      annotations:
-        eventing.knative.dev/broker.class: MTChannelBasedBroker
-      name: default
-      namespace: default
-    ```
-
-1. Configure the `spec.config` with the details of the ConfigMap that defines the required configuration for the Broker class (e.g. with some Channel configurations in case of the `MTChannelBasedBroker`):
-
-    ```yaml
-    apiVersion: eventing.knative.dev/v1
-    kind: Broker
-    metadata:
-      annotations:
-        eventing.knative.dev/broker.class: MTChannelBasedBroker
-      name: default
-      namespace: default
-    spec:
-      config:
-        apiVersion: v1
-        kind: ConfigMap
-        name: config-br-default-channel
-        namespace: knative-eventing
-    ```
-
-For further information about configuring a default Broker class cluster wide or on a per namespace basis, check the [Administrator configuration options](../configuration/broker-configuration.md#configuring-the-broker-class).