Cleanup: trailing space

doc/python_api/rst/info_gotchas_armatures_and_bones.rst

@@ -97,5 +97,3 @@ clearly separates sections of the code which operate in different modes.
 
 This is mainly an issue with Edit-Mode since pose data can be manipulated without having to be in Pose-Mode,
 yet for operator access you may still need to enter Pose-Mode.
-
-

doc/python_api/rst/info_gotchas_file_paths_and_encoding.rst

@@ -73,4 +73,3 @@ to keep it short about encoding problems -- here are some suggestions:
    when reading some input it's less trouble to read it as binary data
    though you will still need to decide how to treat any strings you want to use with Blender,
    some importers do this.
-

doc/python_api/rst/info_gotchas_internal_data_and_python_objects.rst

@@ -209,4 +209,3 @@ there is also no guaranteed compatibility in future releases.
 .. code-block:: python
 
    bpy.ops.wm.redraw_timer(type='DRAW_WIN_SWAP', iterations=1)
-

doc/python_api/rst/info_gotchas_meshes.rst

@@ -109,4 +109,3 @@ the choice mostly depends on whether the target format supports n-gons or not.
   in fact this is the only place where their use is encouraged.
 - BMesh-Faces can work for exporting too but may not be necessary if polygons can be used
   since using BMesh gives some overhead because it's not the native storage format in Object-Mode.
-