docs: Fix documentation

docs/source/configuration/sync.rst

@@ -47,7 +47,7 @@ by providing a dictionary of serializers with the serializer as key and the
 configuration of the serializer as value. For example ``Class`` using the
 ``add_custom_diagrams`` serializer to render the tree view diagram from the
 ``tree_view`` Capella attribute into a custom field with the ID ``tree_view``
-and title ``Tree View ``:
+and title ``Tree View``:
 
 .. literalinclude:: ../../../tests/data/model_elements/config.yaml
    :language: yaml
@@ -58,7 +58,7 @@ or ``SystemFunction`` with the ``add_custom_diagrams`` serializer using
 
 .. literalinclude:: ../../../tests/data/model_elements/config.yaml
    :language: yaml
-   :lines: 69-72
+   :lines: 57-72
 
 If a serializer supports additional parameters this will be documented in the
 supported capella serializers table in :ref:`Model synchronization
@@ -76,7 +76,7 @@ to the desired Polarion type.
 
 .. literalinclude:: ../../../tests/data/model_elements/config.yaml
    :language: yaml
-   :lines: 84-99
+   :lines: 79-104
 
 For the ``PhysicalComponent`` you can see this in extreme action, where based
 on the different permutation of the attributes actor and nature different
@@ -93,14 +93,14 @@ Links can be configured by just providing a list of strings:
 
 .. literalinclude:: ../../../tests/data/model_elements/config.yaml
    :language: yaml
-   :lines: 36-37
+   :lines: 35-37
 
 However there is a more verbose way that gives you the option to configure the
 link further:
 
 .. literalinclude:: ../../../tests/data/model_elements/config.yaml
    :language: yaml
-   :lines: 59-68
+   :lines: 58-68
 
 The links of ``SystemFunction`` are configured such that a ``polarion_role``,
 a separate ``capella_attr``, an ``include``, ``link_field`` and