Skip to content

Backport getting-started typo fixes to 3.27#3722

Merged
olehermanse merged 1 commit into
3.27from
pr-backport-getting-started-typos-3.27-v2
Jul 3, 2026
Merged

Backport getting-started typo fixes to 3.27#3722
olehermanse merged 1 commit into
3.27from
pr-backport-getting-started-typos-3.27-v2

Conversation

@claude

@claude claude Bot commented Jul 3, 2026

Copy link
Copy Markdown

Requested by Ole Herman · Slack thread

Backport to 3.27 (with -x cherry-pick provenance) of master PR #3718.

This cherry-picks the getting-started typo fixes onto the 3.27 release branch. The commit was created with git cherry-pick -x -m 1, so its message carries a (cherry picked from commit 75836ece4053ba620337141c4d96904e469a09a4) line for backport traceability.

Before / After

Several small wording and formatting typos in the getting-started docs are corrected so the text reads correctly and links/markdown render properly.

Per-file fixes

  • content/getting-started/01-installing-cfengine/general-installation/_index.markdown — two occurrences: "adjusting its settings" -> "adjusting their settings" (subject is plural "daemons").
  • content/getting-started/01-installing-cfengine/general-installation/installation-enterprise-free.markdown — fixed broken Markdown link [here] (url) -> [here](url) (removed stray space that broke the link).
  • content/getting-started/01-installing-cfengine/pre-installation-checklist/vi-quick-start-guide.markdown — two sentence-start capitalizations: "type" -> "Type" (Step 2) and "exit vi" -> "Exit vi" (Step 6).
  • content/getting-started/03-adding-modules.markdown — image alt text typo "maserfiles" -> "masterfiles".

Diff stat: 4 files changed, 6 insertions(+), 6 deletions(-).


Generated by Claude Code

Fix typos in getting-started documentation

(cherry picked from commit 75836ec)
@olehermanse olehermanse merged commit 05f11e6 into 3.27 Jul 3, 2026
4 checks passed
@olehermanse olehermanse deleted the pr-backport-getting-started-typos-3.27-v2 branch July 3, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants