diff --git a/docs/source/design/float/decisions/pluggable-broker.md b/docs/source/design/float/decisions/pluggable-broker.md
index dd8f47886b..e747dfd68e 100644
--- a/docs/source/design/float/decisions/pluggable-broker.md
+++ b/docs/source/design/float/decisions/pluggable-broker.md
@@ -18,7 +18,7 @@ A decision on when to prioritise implementation of a pluggable broker has implic
 
 1.    Meshes with business opportunities from HPE and Solace Systems.
 2.    Would allow us to interface to existing Bank middleware.
-3.    Would allow us to switch away from Artemis if we need higherperformance.
+3.    Would allow us to switch away from Artemis if we need higher performance.
 4.    Makes our AMQP story stronger.
 
 #### Disadvantages
@@ -35,7 +35,7 @@ A decision on when to prioritise implementation of a pluggable broker has implic
 
 #### Disadvantages
 
-1. Have to take care that we have sufficient abstractions that thingslike CORE connections can be replaced later.
+1. Have to take care that we have sufficient abstractions that things like CORE connections can be replaced later.
 2. Leaves HPE and Solace hanging even longer.
 
 
@@ -53,8 +53,6 @@ A decision on when to prioritise implementation of a pluggable broker has implic
 
 3. Probably limits our maximum messaging performance longer term.
 
-   ​
-
 
 ## Recommendation and justification
 
@@ -64,4 +62,4 @@ Proceed with Option 2 (defer development of pluggable brokers until later)
 
 ## Decision taken
 
-Decision still required.
\ No newline at end of file
+Decision still required.