docs: Update docs/decisions/0017-generalized-containers.rst

docs/decisions/0017-generalized-containers.rst

@@ -47,8 +47,8 @@ Decisions
 
 - A new version is created if and only if the container itself changes (e.g., title, ordering of contents, adding or removing content) and not when its content changes (e.g., a component in a Unit is updated with new text).
 - Changes to the order of members within a container require creating a new version of the container with the new ordering.
-- Changes in pinned published or draft states require creating a new version of the container to maintain the state of the content for the previous version.
 - Each time a new version is created because of metadata changed, its members are copied from the previous version to preserve the state of the content at that time.
+- Changes in pinned published or draft states require creating a new version of the container to maintain the state of the content for the previous version.
 - When using version-agnostic references to members, no new version is created when members change since the latest draft or published state is always used.
 - If a member is soft-deleted, the container will create a new version with the member removed.