Dhairya-007 opened a new pull request, #29648:
URL: https://github.com/apache/camel/pull/29648
16 misspellings in the user manual, one commit per page or group of pages.
`Initally`/`hauwei`, `implemetations`, `impelentation`, `optmized`,
`exection strackframe`, `indempotent`, `instead fo the`, `partions`,
`unnessasary`, `specifed`, `recieve`, `commponent`, `acces`, `requst`, and in
the release guide the section heading `== Prequisites` and `Everytime`.
The `[[ReleaseGuide-Prequisites]]` anchor above that heading is deliberately
left as it is, so any external link to it keeps working; nothing in `docs/`
cross-references the heading text.
### Deliberately left alone
These all look like typos to a spell checker and are correct as written:
- `camel ps --sort=nmae` in the 4.24 guide — the example of an **unknown**
sort key, which is the behaviour being described.
- `` `chiper` `` in the Camel 3 migration guide — the sentence is "fix the
typo `chiper` to `cipher`".
- `value="history,adress"` in the 3.2 guide — a field name in a user's own
XStream example.
- `siz` in the jbang source-editor page — the example of an option typo the
editor reports.
- `Adviced endpoint` in `advice-with.adoc` — quoted log output;
`InterceptSendToMockEndpointStrategy` really logs it that way, so the page
must match. `adviced`/`advicing` elsewhere on that page is Camel's own
`adviceWith` vocabulary and is left consistent with it.
- `vertx`/`Vertx`/`VertX`, `afterAll`, `marshalIn`, `inout`, `.ans` —
product,
API and file names.
- `useable`, `unparseable`, `browseable` — accepted variant spellings.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
