Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/docs/how-to/model-products.md`:
- Around line 153-161: The phrase "all three components plus the aggregator" is
misleading because the example table shows only three entries; update the
wording near the verification output (the sentence referencing "all three
components plus the aggregator" or similar text) to explicitly list or rephrase
to "backend, frontend, and the aggregator component" (or "three components
including the aggregator") so it matches the example table header "COMPONENT │
VERSION │ PROVIDER" and the shown entries.

In `@content/docs/how-to/use-component-constructor.md`:
- Around line 355-357: Update the example shell snippet that sets VERSION and
IMAGE_VERSION so the command is executable by adding the repository target;
change the command using the existing symbols (VERSION, IMAGE_VERSION and the
command invocation `ocm add cv`) to include the same repository flag used
earlier (e.g., `--repository ./transport-archive`) so the snippet runs as shown.
- Around line 186-190: Replace the incorrect artifact type casing "fileSystem"
with the canonical lowercase "filesystem" in this document; locate the two
occurrences where the YAML block contains "type: fileSystem" (the same blocks
that include "input:" and "type: dir/v1") and update them to "type: filesystem"
so all artifact type entries match the OCM specification.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/docs/how-to/use-component-constructor.md`:
- Line 52: Update the tip text that currently reads “The `#yaml-language-server`
comment enables auto-completion and inline validation in editors that support
the YAML Language Server.” Replace the redundant phrase “YAML Language Server”
with a tightened alternative such as “YAML Server” or “YAML support” and ensure
the sentence still references the `#yaml-language-server` comment and the schema
URL at ocm.software/schemas/configuration-schema.yaml so editors and schema info
remain clear.

---

Duplicate comments:
In `@content/docs/how-to/use-component-constructor.md`:
- Line 356: The env-var command shown ("VERSION=1.2.3 IMAGE_VERSION=6.9.4 ocm
add cv") is missing the repository target; update that snippet to include the
repository flag so it is runnable in-place by changing it to "VERSION=1.2.3
IMAGE_VERSION=6.9.4 ocm add cv --repository ./transport-archive".
- Line 86: Several examples use inconsistent casing for the artifact type (some
use "type: fileSystem" while others use "type: filesystem"); update all
occurrences of the artifact type to the canonical lowercase "filesystem"
(replace the literal strings "type: fileSystem" at the example instances with
"type: filesystem" so the constructor examples are consistent and valid) and
double-check other example blocks for any remaining "fileSystem" variants.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@content/docs/how-to/use-component-constructor.md`:
- Line 356: The env-var example command is missing the repository target; update
the command string "VERSION=1.2.3 IMAGE_VERSION=6.9.4 ocm add cv" to include the
repository flag by appending "--repository ./transport-archive" so the example
is runnable in-place (i.e., change the example invocation to "VERSION=1.2.3
IMAGE_VERSION=6.9.4 ocm add cv --repository ./transport-archive").
- Line 86: Replace the non-canonical casing "fileSystem" with the standard
"filesystem" wherever it appears in the document (specifically the YAML/config
key usage shown as `type: fileSystem` on line examples around the doc); search
for the exact token "fileSystem" and update to "filesystem" so all `type:`
entries and examples are consistent across the file (including the occurrences
noted near the two locations).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/docs/how-to/model-products.md`:
- Around line 220-224: There are multiple consecutive blank lines just before
the closing step tag "{{< /step >}}"; edit the markdown block around that
closing tag and remove the extra empty lines so there is only a single blank
line immediately before "{{< /step >}}", ensuring the steps markup remains
correctly formatted.

In `@content/docs/reference/component-descriptor.md`:
- Around line 136-139: The markdown list of examples
(`github.com/open-component-model/ocm` and `acme.org/platform/frontend`) lacks a
blank line before it; insert a single blank line immediately above the list so
the Examples: paragraph and the subsequent bullet list are separated to satisfy
MD032 (i.e., ensure there is an empty line between the preceding paragraph and
the "- `github.com/open-component-model/ocm`" / "- `acme.org/platform/frontend`"
list).

In `@content/docs/tutorials/advanced-component-constructor.md`:
- Around line 419-423: There are multiple consecutive blank lines between the
closing </details> tag and the {{< /step >}} token in
content/docs/tutorials/advanced-component-constructor.md; open that section and
remove the extra empty lines so there is only a single blank line separating
</details> and {{< /step >}}.
- Around line 45-48: There's an extra blank line(s) between the paragraph "Each
box is an independent component version. Arrows represent `componentReferences`.
Leaf components carry the actual resources; parent components aggregate them."
and the "## Scenario" header; remove the extra blank line(s) so there is exactly
one blank line separating that paragraph and the "## Scenario" heading to
satisfy Markdown linting.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/docs/how-to/model-products.md`:
- Around line 25-32: The example topology shown in the mermaid diagram (nodes P,
B, F, C where P is "product v2.0.0" and C is "cache v2.0.0") is inconsistent
with the walkthrough steps and expected outputs because the `cache` component
(C) is never created; update the guide to keep the example consistent by either
removing the cache node from the diagram and any mentions of `cache` in the
constructor text, or adding explicit steps that create and register the `cache`
component (matching the `componentReferences` example) and updating the expected
outputs to include `cache v2.0.0` so the diagram, constructor, and walkthrough
all match.

In `@content/docs/reference/component-descriptor.md`:
- Around line 365-367: The "Full Example" section claims the example combines
"all sections above" but omits nestedDigests; either update the example under
the "Full Example" heading to include a representative nestedDigests entry
(matching the document's nestedDigests schema) or change the wording to
something like "most top-level sections above" and explicitly note that
nestedDigests is excluded; refer to the "Full Example" heading and the
nestedDigests field when making the change.

In `@content/docs/tutorials/advanced-component-constructor.md`:
- Around line 404-416: Update the "Expected output" for the `ocm get cv
acme-platform/transport-archive//github.com/acme.org/frontend:1.5.0 -o yaml`
verification to list the actual frontend resources (only `chart` and `image`)
and provider info (`acme.org`), removing `manifests` (which belongs to the
backend); locate the block that describes the expected component descriptor
output and change the bullet list from "- The `resources` section listing
`manifests`, `chart`, and `image`" to "- The `resources` section listing `chart`
and `image`" while keeping the provider note.
- Around line 187-188: The artifact entry using "type: filesystem" is invalid;
update the artifact type to the canonical name "directoryTree" (or the alias
"fileSystem") for the artifact with name "migrations" (and the other occurrence
noted around lines 494-495). Modify the YAML entries that currently read 'type:
filesystem' to 'type: directoryTree' (or 'type: fileSystem' if you prefer the
alias) so they match the component-descriptor artifact types.