fixes typos and minor reformatting issues

Author: davidbreitgand

docs/proposals/XXXX-pluggable-bbr-framework/README.md

@@ -51,11 +51,17 @@ In addition, a `PluginsChain` interface is defined to define an order of plugin
 
 Depending on a `BBRPlugin` functionality and implementation, the plugin might require full or selective body parsing. To save the parsing overhead, if there is at least one `BBRPlugin` in the `PluginsChain` that requires full body parsing, the parsing is performed only once into a shared official appropriate `openai-go` struct (either `openai.CompletionNewParams`  or `openai.ChatCompletionNewParams` depending on the request endpoint). This struct is shared for read-only to all plugins in the chain. Each `BBRplugin` receives the shared struct by value. If a plugin needs to mutate the body, in the initial implementation, it MUST work on its own copy, and the a mutated body is returned separately by each plugiin.
 
-### Suggested BBR Pluggable Framework Interfaces
+### Suggested Components
 
 The sketch of the proposed framework is shown in the figure below.
 <img src="./images/pluggable-framework-architecture-sketch.png" alt="Components of the proposed framework" width="1000" />
 
+
+The following figure shows a sequence diagram that illustrates the components interaction
+<img src="./images/bbr-pluggable-framework-sequence-diagram.png" alt="Sequence diagram" width="1000" />
+
+### Suggested BBR Pluggable Framework Interfaces
+
 ```go
 //Base BBRPlugin interface
 type BBRPlugin interface {
@@ -141,9 +147,6 @@ var SupportedInterfaces = map[string][]string{
 }
 ```
 
-The figure below shows a sequence diagram that illustrates the components interaction
-<img src="./images/bbr-pluggable-framework-sequence.png" alt="Sequence diagram" width="1000" />
-
 ### Implementation Phases
 
 The pluggable framework will be implemented iteratively over several phases.