Fix typographical errors in administration section #197

brettweir · 2026-07-13T01:21:59Z

brettweir commented

2026-07-13 01:21:59 +00:00

This pull request makes the following changes to the administration section of the documentation:

Fix spelling and punctuation errors.
Switch to US English spellings where applicable.
Avoid the use of hidden/ambiguous Unicode characters where ASCII characters would suffice.

I tried to take a light-touch approach here, but happy to update the PR if any changes are too aggressive.

This pull request makes the following changes to the **administration** section of the documentation: - Fix spelling and punctuation errors. - Switch to US English spellings where applicable. - Avoid the use of hidden/ambiguous Unicode characters where ASCII characters would suffice. I tried to take a light-touch approach here, but happy to update the PR if any changes are too aggressive.

brettweir force-pushed proofread-administration from b55888951b to db003c5728

2026-07-13 01:22:45 +00:00

Compare

goroboro approved these changes

2026-07-13 16:54:49 +00:00

goroboro left a comment

Looks good to me, but we should revisit that versioning line.

modules/ROOT/pages/administration/virtual-routing-bridge.adoc

					
				@ -27,3 +27,3 @@

				== Prerequisites

				. Fully updated Fedora Server, any version of F33 or newer, preferrable F38.

				. Fully updated Fedora Server, any version of F33 or newer, preferable F38.

Whew F38 is long out of support. I realize this is a typographical commit, but maybe we should just remove the version info here? Fully updated should imply that you you're on the latest release. Or maybe change to:
Fully updated Fedora Server, preferably on the latest supported Fedora release.

Whew F38 is long out of support. I realize this is a typographical commit, but maybe we should just remove the version info here? Fully updated should imply that you you're on the latest release. Or maybe change to: Fully updated Fedora Server, preferably on the latest supported Fedora release.

Yeah, this kind of callout goes stale super fast. I prefer to only mention version numbers to document when specific features become available, or not at all.

Out of scope for this PR though.

Yeah, this kind of callout goes stale super fast. I prefer to only mention version numbers to document when specific features become available, or not at all. Out of scope for this PR though.