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

Inline comments:
In `@content/docs/tutorials/deploy-with-controllers-advanced.md`:
- Line 345: The file ends without a trailing newline; update the document
"deploy-with-controllers-advanced.md" by adding a single newline character after
the final line ("Complete with configuration and transfer to a private registry,
and setting helm values for our deployment to boot.") so the file terminates
with exactly one trailing newline.
- Line 207: Replace the backtick placeholder links for "controller chain" and
"Deployer" with the actual documentation URLs or internal doc anchors: find the
canonical docs/pages that describe the controller chain and the Deployer (search
for pages mentioning "controller chain" and "Deployer" in the docs site) and
update the two link targets in the line containing "bootstrap the RGD" so the
markdown reads [controller chain](<actual-doc-url>) and
[Deployer](<actual-doc-url>), preserving the existing link text and formatting.
- Line 21: The markdown references the link labels [Kro] and [Flux] but no link
definitions are present; add link reference definitions for these labels (e.g.,
at the end of the document) pointing to the official Kro and Flux documentation
URLs so the inline references resolve; update the file's markdown to include
lines like "[Kro]: <KRO_DOC_URL>" and "[Flux]: <FLUX_DOC_URL>" (replace with the
correct documentation URLs) so the links render correctly.
- Line 200: Remove the extra blank line before the callout shortcode "{{<callout
context=\"note\">}}" in the Markdown block so there are no multiple consecutive
blank lines; edit the paragraph containing the trailing triple-backtick and the
following blank line and delete one of the blank lines so the callout
immediately follows the content.
- Line 12: The Markdown link for the Deployer is malformed and uses a
placeholder; replace the escaped-backtick link segment
"`kubernetes-deployment.yaml placeholder`" with a proper Markdown link target to
the Deployer docs (e.g., [Deployer](<correct-deployer-doc-url>)) so the sentence
reads "...The Deployer extracts and applies it automatically." Keep the
surrounding text and mention of ResourceGraphDefinition and localization intact
(search for "ResourceGraphDefinition" and "Deployer" to locate the line).
- Around line 218-219: The repository example uses the legacy type value; locate
the repositorySpec block that currently reads "type: OCIRegistry" (search for
repositorySpec and the literal "OCIRegistry") and change it to the preferred
"type: OCIRepository" so it matches the other tutorials and the component
descriptor documentation.

In `@content/docs/tutorials/deploy-with-controllers.md`:
- Line 259: The sentence contains an unresolved placeholder "<deployer concept
placeholder>" that needs to be replaced with the real Deployer concept
documentation link; locate the Deployer concepts page that explains ApplySets
(or the specific "ApplySets" subsection), then replace the placeholder with the
proper Markdown link text and URL (e.g., "Deployer concepts — ApplySets" or
similar) in the sentence that references ApplySets so the line reads something
like: To understand ... please visit the [Deployer concepts —
ApplySets](<actual-doc-url>) page.
- Line 44: Remove the extra consecutive blank line in the Markdown file
deploy-with-controllers.md at the indicated location so there is only a single
blank line between paragraphs; edit the section around the blank line to
collapse the two empty lines into one to satisfy Markdown formatting rules.
- Around line 206-207: Update the Repository resource snippet so the
repositorySpec uses the same resource type as other docs: change the property
value "type: OCIRepository" to "type: OCIRegistry" (the snippet containing
baseUrl: $OCM_REPO and type: OCIRepository should be updated), ensuring the
Repository resource examples match deploy-helm-chart-bootstrap.md and other
guides.

---

Nitpick comments:
In `@content/docs/tutorials/configure-credentials-for-controllers.md`:
- Around line 17-20: The manual TOC currently includes a self-referencing
top-level bullet linking to "#how-to-configure-credentials" which is redundant
because Hugo's automatic TOC is enabled (front matter key toc: true); remove the
single self-referencing bullet ("How to Configure Credentials?") from the manual
list (or remove the entire manual list if you prefer auto-TOC only) so that only
the subsection links ("Create a Kubernetes Secret of Type `dockerconfigjson`"
and "Create a Kubernetes Secret or Configmap from an `.ocmconfig` file") remain;
locate the markdown block containing the manual TOC near the
"#how-to-configure-credentials" header and delete the redundant entry.

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

Inline comments:
In `@content/docs/how-to/deploy-manifests-with-deployer.md`:
- Around line 220-224: Add a blank line before the bullet list that starts with
"Repository — points to the OCM repository" so the Markdown linter recognizes
it; edit the block containing the lines "Repository", "Component", "Resource",
and "Deployer" and insert one empty line immediately above the first list item
to satisfy the lint rule.

---

Nitpick comments:
In `@content/docs/getting-started/setup-controller-environment.md`:
- Around line 12-20: Replace the informal "k8s" in the callout text with the
full "Kubernetes" for style consistency—specifically update the phrase "raw k8s
deployment" inside the callout block to "raw Kubernetes deployment" (or "a raw
Kubernetes deployment" to fit grammar) and ensure other nearby prose in the same
callout uses the same capitalization/term to match the project’s documentation
convention.

In `@content/docs/how-to/deploy-manifests-with-deployer.md`:
- Line 17: The line "Any extra RBAC configured by following [Custom RBAC
guide]({{< relref "custom-rbac.md" >}})" implies RBAC is required; update it to
clarify it is optional, e.g., prepend "Optional:" or rephrase to "Any additional
RBAC (optional) — see [Custom RBAC guide]({{< relref "custom-rbac.md" >}})" so
readers know RBAC is only needed if you require custom permissions; modify that
exact sentence in the document.

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

Inline comments:
In `@content/docs/tutorials/deploy-helm-chart-bootstrap.md`:
- Line 50: The sentence currently uses the non-preferred spelling "hardcoded";
update the text in deploy-helm-chart-bootstrap.md (the sentence "This ensures
your deployment always uses images from the current registry, not hardcoded
original locations.") to use "hard-coded" instead of "hardcoded" so it passes
spellcheck.
- Around line 13-16: Insert a blank line before each bullet list that currently
follows immediately after lead-in text—specifically the list starting with "- An
OCM component containing a Helm chart, an image reference, and deployment
instructions" (and the similar lists beginning with "- A running Podinfo
application" and "- Understanding of how localization keeps image references in
sync after transfers"), as well as the other list blocks noted in the comment;
update those list blocks by adding a single empty line above each list so
markdownlint MD032 passes.

---

Duplicate comments:
In `@content/docs/how-to/deploy-manifests-with-deployer.md`:
- Around line 224-228: Add a blank line before the list that starts with "-
**Repository** — points to the OCM repository" (the "resource chain" list under
its heading) and likewise add a blank line before the list at the later section
around the manifest examples (the list starting at lines ~280–283) so both list
blocks are preceded by an empty line to satisfy markdownlint MD032 and CI Verify
Markdown; locate these lists by the bullet text ("Repository", "Component",
"Resource", "Deployer") and the subsequent manifest/example bullet block and
insert a single blank line immediately above each.

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

Inline comments:
In `@content/docs/getting-started/deploy-helm-chart.md`:
- Around line 130-131: Update the wording that currently says "your GitHub
repository `https://github.com/$GITHUB_USERNAME?tab=packages`" to clarify this
is the account-level Packages page (not a repository page); locate the sentence
referencing the package
`component-descriptors/ocm.software/ocm-k8s-toolkit/simple` and change phrasing
to something like "go to your GitHub account Packages tab
(https://github.com/$GITHUB_USERNAME?tab=packages), select the package ... and
under 'Package settings' change the visibility to `public`" so readers know to
look at the account packages view rather than a repository.

In `@content/docs/getting-started/setup-controller-environment.md`:
- Around line 104-106: Update the broken RBAC link inside the "Security
consideration" callout by replacing the old URL
"https://kro.run/docs/concepts/access-control" with the current access-control
page "https://kro.run/docs/advanced/access-control" in the callout block (the
block starting with {{< callout context="caution" title="Security consideration"
>}}) so the markdown link check passes.

---

Duplicate comments:
In `@content/docs/tutorials/deploy-helm-chart-bootstrap.md`:
- Line 63: Update the wording in the sentence containing "hardcoded original
locations" to use the preferred spelling "hard-coded" (i.e., change "hardcoded
original locations" to "hard‑coded original locations") so the sentence reads:
"This ensures your deployment always uses images from the current registry, not
hard‑coded original locations." Locate the phrase in the
deploy-helm-chart-bootstrap.md content and replace the single word accordingly.

---

Nitpick comments:
In `@content/docs/getting-started/setup-controller-environment.md`:
- Around line 13-15: Reword the awkward tip that currently says “raw k8s
deployment from an ocm resource” for clarity and readability; replace the
sentence with something like: “If you’re only deploying a raw Kubernetes
Deployment manifest provided by an OCM resource, you can skip kro and Flux.”
Locate and update the sentence that contains the phrase "raw k8s deployment from
an ocm resource" to use the clearer wording and ensure the tip reads as a single
concise sentence.

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

Inline comments:
In `@content/docs/tutorials/deploy-helm-chart-bootstrap.md`:
- Around line 362-369: Change the ordered-list numbering to use "1." for every
item to satisfy markdownlint MD029: locate the two list items that start with
"Flux OCIRepository" (the block showing secretRef: name: ghcr-secret) and "Pod
imagePullSecrets" (the HelmRelease values guidance) and replace their current
numeric prefixes (e.g., "2." and "3.") with "1." so the list uses the required
1/1/1 style.

---

Duplicate comments:
In `@content/docs/getting-started/deploy-helm-chart.md`:
- Around line 130-131: The text incorrectly calls the account-level Packages
page a "GitHub repository" — update the sentence that references
`https://github.com/$GITHUB_USERNAME?tab=packages` and the phrase “in your
GitHub repository” to make clear this is the account-level Packages tab (not a
repository page); replace with wording like “go to your GitHub account Packages
page (`https://github.com/$GITHUB_USERNAME?tab=packages`)” and then instruct the
user to select the package
`component-descriptors/ocm.software/ocm-k8s-toolkit/simple` and change its
visibility to `public` under Package settings to avoid navigation confusion.