Update save_and_load.adoc

Fixed broken new lines.

src/docs/asciidoc/jme3/advanced/save_and_load.adoc

@@ -86,8 +86,10 @@ Here you see why we save user data inside spatials – so it can be saved and lo
 
 JME's BinaryExporter can write standard Java objects (String, ArrayList, buffers, etc), JME objects (Savables, such as Material), and primitive data types (int, float, etc). If you are using any custom class together with a Spatial, then the custom class must implement the `com.jme3.export.Savable` interface. There are two common cases where this is relevant:
 
-*  The Spatial is carrying any <<jme3/advanced/custom_controls#,Custom Controls>>. +Example: You used something like `mySpatial.addControl(myControl);`
-*  The Spatial's user data can contain a custom Java object. +Example: You used something like `mySpatial.setUserData(“inventory, myInventory);`
+*  The Spatial is carrying any <<jme3/advanced/custom_controls#,Custom Controls>>. +
+Example: You used something like `mySpatial.addControl(myControl);`
+*  The Spatial's user data can contain a custom Java object. +
+Example: You used something like `mySpatial.setUserData(“inventory, myInventory);`
 
 If your custom classes (the user data or the Controls) do not implement Savable, then the BinaryImporter/BinaryExporter cannot save the Spatial!