diff --git a/docs/BinaryProtocol.md b/docs/BinaryProtocol.md
index d8ec1fd6dd2472582cf3fc44353acf4a5fd50805..3d3031533c41e5936977485181b89a73ac513dce 100644
--- a/docs/BinaryProtocol.md
+++ b/docs/BinaryProtocol.md
@@ -144,7 +144,7 @@ When compression is enabled, the whole batch will be compressed at once.
 After opening a TCP connection to a broker, typically on port 6650, the client
 is responsible to initiate the session.
 
-![Connect interaction](img/Binary Protocol - Connect.png)
+![Connect interaction]("img/Binary%20Protocol%20-%20Connect.png")
 
 After receiving a `Connected` response from the broker, the client can
 consider the connection ready to use. Alternatively, if the broker doesn't
@@ -209,7 +209,7 @@ authorized to publish on the topic.
 Once the client gets confirmation of the producer creation, it can publish
 messages to the broker, referring to the producer id negotiated before.
 
-![Producer interaction](img/Binary Protocol - Producer.png)
+![Producer interaction](img/Binary%20Protocol%20-%20Producer.png)
 
 ##### Command Producer
 
@@ -322,7 +322,7 @@ A consumer is used to attach to a subscription and consume messages from it.
 After every reconnection, a client needs to subscribe to the topic. If a
 subscription is not already there, a new one will be created.
 
-![Consumer](img/Binary Protocol - Consumer.png)
+![Consumer](img/Binary%20Protocol%20-%20Consumer.png)
 
 #### Flow control
 
@@ -471,7 +471,7 @@ connect to, or a broker hostname to which retry the lookup.
 The `LookupTopic` command has to be used in a connection that has already
 gone through the `Connect` / `Connected` initial handshake.
 
-![Topic lookup](img/Binary Protocol - Topic lookup.png)
+![Topic lookup](img/Binary%20Protocol%20-%20Topic%20lookup.png)
 
 ```json
 CommandLookupTopic {