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

Inline comments:
In `@content/docs/concepts/credential-system.md`:
- Line 143: Replace the fragile relative relref tag `{{< relref
"configure-credentials-for-controllers.md" >}}` with an absolute docs path used
across the PR (e.g. `{{< relref
"docs/concepts/configure-credentials-for-controllers.md" >}}`) so the link is
stable across sections; update the markdown line that currently reads
`[Credentials for OCM Controllers]({{< relref
"configure-credentials-for-controllers.md" >}})` to use the absolute relref
string instead.

In `@content/docs/how-to/configure-multiple-credentials.md`:
- Around line 82-107: The docs example uses the deprecated field name
`pathprefix` for OCIRepository identities; update the example and explanatory
text to use the v2 `path` field with glob semantics instead of `pathprefix`, and
adjust the explanatory lines (e.g., "Uses `pathprefix`..." and the
"Identity/Matches" text) to describe `path` glob matching and the precedence
rule (more specific `path` patterns checked first); ensure the example consumer
identity still references `type: OCIRepository`, `hostname: ghcr.io` and the
pattern (e.g., a glob-style `path`) so the snippet and the surrounding prose are
consistent with v2.
- Line 206: The relref link for "OCM Credentials" is missing a leading slash;
update the link target in the "[OCM Credentials]" line so the relref uses a
leading '/' (e.g., change {{< relref "docs/concepts/credential-system.md" >}} to
include the leading slash) to match other docs and ensure correct resolution by
the relref helper.

In `@content/docs/tutorials/credential-resolution.md`:
- Around line 263-289: The docs incorrectly claim that OCM "treats `oci` like
`https` and explicitly sets port 443"; update Example D and the surrounding
explanation to state that the hostpath identity builder does not auto-fill a
port for the `oci` scheme (only `https`→443 and `http`→80 have defaults). In the
paragraph referencing `oci://` behavior (Example D), remove the sentence about
treating `oci` like `https` and replace it with: "Unlike `https` or `http`, the
`oci` scheme has no built-in default port; if a port is not included in the URL
the port attribute remains empty." Ensure the table and the example
YAML/description remain consistent with this corrected behavior.

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

Duplicate comments:
In `@content/docs/concepts/credential-system.md`:
- Line 143: The link "[Credentials for OCM Controllers]({{< relref
"configure-credentials-for-controllers.md" >}})" uses a relative relref; update
it to the project's standardized absolute relref form (replace the relative
target "configure-credentials-for-controllers.md" with the absolute path used
across the PR) so the entry becomes an absolute relref consistent with other
docs.

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

Inline comments:
In `@content/docs/tutorials/credential-resolution.md`:
- Around line 200-203: The table row for the Request `ghcr.io/my-org/repo`
(Example B2) contradicts the documented "first-match-wins" rule: update that row
so the Result is the Consumer A credential (`org-user`) and change the Why
column to reflect "A matches first (first-match-wins)" instead of saying B is
more specific; ensure the sample config labels ("Consumer A", "Consumer B") and
the Result/Why text align with the first-match-wins rule.

---

Outside diff comments:
In `@content/docs/tutorials/configure-credentials-for-controllers.md`:
- Around line 66-83: The example YAML uses v1 fields but the docs reference the
v2 credential system; update the sample to the v2 schema by changing the
resource version from generic.config.ocm.software/v1 to /v2 and by replacing the
v1-style credential fields shown (the credentials.config.ocm.software block,
consumers.identity keys: type, scheme, hostname, pathprefix, and
credentials.properties username/password) with their v2 equivalents per the v2
credential schema; ensure the sample reflects v2 field names and structure
exactly (e.g., new top-level version and the v2 layout for credential
references/secrets) so the snippet matches the rest of the docs.

---

Duplicate comments:
In `@content/docs/tutorials/credential-resolution.md`:
- Around line 263-266: The paragraph incorrectly claims OCM treats the `oci`
scheme like `https` and explicitly sets port 443; update the text in the
credential-resolution doc to remove that claim and instead state that the
identity matcher only has built-in default ports for `https` → `443` and `http`
→ `80`, and that `oci` has no default port so matching relies on explicit ports
when present. Edit the sentences referencing `oci://` and port 443 (the lines
describing OCM building a lookup identity from an `oci://` URL) to clarify that
OCM does not implicitly map `oci` to `https`/443 and ensure the example
explanation reflects that matching works only when both sides explicitly include
the same port.