Apply suggestions from code review

Co-authored-by: Simon Gerber <simon.gerber@vshn.ch>

Author: HappyTetrahedron

docs/modules/SDDs/pages/0033-commodore-component-instance-versioning.adoc

@@ -1,8 +1,8 @@
 = SDD 0033 - Commodore Component Instance Versioning
 
 :sdd_author:    Aline Abler
-:sdd_owner:     Aline Abler
-:sdd_reviewers: SIG
+:sdd_owner:     Aldebaran
+:sdd_reviewers: Simon Gerber
 :sdd_date:      2025-01-08
 :sdd_status:    draft
 include::partial$meta-info-table.adoc[]
@@ -34,7 +34,7 @@ Commodore will leverage the existing configuration options in `.parameters.compo
 Instance versions can be specified in `.parameters.components.<instance-name>` and override the value specified in `.parameters.components.<component-name>`.
 Even if all instances provide their own version, a version for the base component (`.parameters.components.<component-name>`) must still be specified.
 
-Component authors must explicitly declare that their component supports multi-versioning.
+Component authors must explicitly declare that their component supports multi-versioning by setting component parameter `_metadata.multi_versioning=true`.
 In a valid catalog, all used versions of the same component must advertise this support.
 
 Components with multi-versioning support must ensure they create no file conflicts when downloading dependencies.
@@ -66,9 +66,10 @@ This might force a component author to remove multi-version support in higher co
 
 === Automatically detecting multi-version support
 
-It could be possible to automatically determine whether a component supports multi-versioning, by way of checking whether the `${_base_directory}` parameter is used in the component's compile configuration.
+We could try to automatically determine whether a component supports multi-versioning, by way of checking whether the `${_base_directory}` parameter is used in the component's compile configuration and for Jsonnet expressions that refer to downloaded data.
 However, automatically declaring components to be "safe for multi-versioning" carries some risk - even if a component is configured accordingly, it is not guaranteed that its provided Jsonnet libraries and/or its Jsonnet dependencies work if used across versions.
-Therefore, we deem it safer to let component authors decide if multi-versioning is safe to use for their component.
+Additionally, so far we've defined explicit flags for components to indicate that they support optional features, such as multiple instances.
+For all of those reasons, we've decided that component authors must explicitly declare whether multi-versioning is safe to use for their component.
 
 === Supporting different versions of Jsonnet dependencies per instance