manual: figures must have empty line before and after their declaration

docs/manual/markdown/docs/architecture.md

@@ -25,7 +25,9 @@ events and data coming from either the Main Application or from BTstack
 via registered packet handlers (PH). BTstack’s Run Loop is responsible
 for providing timers and processing incoming data.
 
-<a name="fig:BTstackArchitecture"></a>![Architecture of a BTstack-based application.](picts/btstack-architecture.png)
+<a name="fig:BTstackArchitecture"></a> 
+
+![Architecture of a BTstack-based application.](picts/btstack-architecture.png)
 
 # Single threaded design
 

docs/manual/markdown/docs/integration.md

@@ -19,6 +19,7 @@ In a single-threaded environment, all application components run on the
 same (single) thread and use direct function calls as shown in Figure [below](#fig:BTstackSingle).
 
 <a name="fig:BTstackSingle"></a>
+
 ![BTstack in single-threaded environment](picts/singlethreading-btstack.png)
 
 BTstack provides a basic run loop that supports the concept of data
@@ -66,4 +67,5 @@ common options:
     non-embedded version of BTstack e.g., on the iPhone. 
     This option requires more code but provides more flexibility.
 
-    ![](picts/multithreading-btdaemon.png)
+    ![](picts/multithreading-btdaemon.png)
+    

docs/manual/markdown/docs/protocols.md

@@ -40,6 +40,7 @@ In the following, we first explain how the various Bluetooth protocols
 are used in BTstack. In the next chapter, we go over the profiles.
 
 <a name="fig:BTstackProtocolArchitecture"></a>
+
 ![Architecture of a BTstack-based application.](picts/btstack-protocols.png)