Welcome to my talk page.
Checking automated grammar and spelling correction with Grammarly
I have looked at some of your initial edits and feel that I need to ask you to not trust Grammarly blindly.
While the very most of the corrections are correct there are some technical terms that Grammarly seems to be unaware of. These are not all that many so far, but they will likely become more.
In Changelog 2.4.0 edit:
- "Ballistic objects can slave to any AI object" should still be "Ballistic objects can be slaved to any AI object"
- "Moved to make based build system" should be "Moved to CMake based build system" (See )
Also typically there would be single whitespace between the equal signs and the title, though that is not visible on the rendered page (it makes the wiki markup slightly easier to read).
Apart from checking what Grammarly suggests or does, feel free to go on. Some of the FlightGear wiki users sometimes use all lowercase, odd punctuation, etc. In addition, the Manual of Style was not around until 2014, and I am certain most users are still oblivious to its existence. Because of these and some other things the wiki is sometimes a bit of a mess.
I have added the above welcome template to all user discussion pages of users having registered after April this year, in the hope that more of the users will understand how a wiki using MediaWiki typically works, and make them aware of the style guide (which I believe might be loosely based on the style guide of the English Wikipedia). Some of us have looked into having it added automatically to discussion pages of new users and adding it to all existing user discussion pages, similar to how they are used on some language editions of Wikipedia. See also FlightGear wiki:Village pump#Welcoming template (permalink).
- @User talk:Johan G Thank you for the advice! Sorry about removing the white spaces from the equals. Will not do that again, as I now see clealy that it confuses other readers. --Axlerate (talk) 05:10, 7 September 2019 (EDT)
I have also looked at the changes by Grammarly. My opinion is that it could be used to identify issues, and then these issues are manually fixed. The reason is because some articles are maintained by speakers of non-American dialects and, if you don't set the dialect correctly, Grammarly will change text which is perfectly correct (this sentence being such an example).
Another issue I found is with these changes. Most of these changes are not correct. These are lists where the sentence continues across the list. So from the following
By submitting a screenshot the submitter agrees to these terms:
you can construct one sentence as
|Note By submitting a screenshot the submitter agrees to these terms: The creator grants the FlightGear project revocable and non-exclusive copyright, which permits the project to persecute copyright infringement on behalf of the screenshot creator.|
After the Grammarly changes, this becomes:
|Note By submitting a screenshot the submitter agrees to these terms: The creator grants the FlightGear project revocable and non-exclusive copyright, which permits the project To persecute copyright infringement on behalf of the screenshot creator.|
This is a big fail for Grammarly, and why page corrections should not be fully automated.
As for protected pages, if the changes are important, I would suggest describing the changes in the 'Discussion' or 'Talk' pages. Admin privileges are rarely given, and only to those people well known to the project (generally after joining one of the core group video conferences). There are also thousands of non-protected pages that could be improved.