Misprints in parameters naming and description

[EgoPingvina]

I worked with QGroundControl and seen some misprints

[hamishwillee]

@RomanBapst @sanderux You OK with the param name changes here? AFAIK parameters can be max 16 chars, and this is IMO better.

[EgoPingvina]

"VT_PUSHER_RMP_DT" - there are exactly 16 characters

[hamishwillee]

Yes @EgoPingvina - I checked and I am happy with that, but I'm not maintainer of this code - hence query to @RomanBapst

[RomanBapst]

@dagar @hamishwillee Do we have a standard procedure how we deal with parameter renaming?
If somebody flies a VTOL with a non-default value of this parameter we will introduce a change to his setting about which he is not aware of, correct?
In this case I think it's not very critical but still I'd like to discuss it.
How about accumulating these changes in a document when we merge them into master? Then those notes can be part of the next release notes.

[hamishwillee]

@dagar @hamishwillee Do we have a standard procedure how we deal with parameter renaming?
If somebody flies a VTOL with a non-default value of this parameter we will introduce a change to his setting about which he is not aware of, correct?
In this case I think it's not very critical but still I'd like to discuss it.
How about accumulating these changes in a document when we merge them into master? Then those notes can be part of the next release notes.

A question for @dagar. On one hand we do need to be able to change things, but on the other, I question whether this particular change is worth the potential impact.

Either way, minimally we need to accumulate the changes and clearly publish them. Even better, a script that people could run to do a migration.
I don't think we do, but you're right that we need to.

[mcsauder]

@EgoPingvina , you'll want to change the parameter name here now as well, (new since you submitted this PR). Hopefully this helps out!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mcsauder]

@EgoPingvina , if you can rebase this PR against current master and fix the additional instance I linked above we could bring up your PR in the next dev call and try to get this merged in. Find me on PX4 slack if you need a hand rebasing.

[mcsauder]

If it's OK, let's close this PR as it's getting old and not being kept updated, and I'll attempt to attend to the requisite work of dealing with renaming parameters in the months ahead and keep track with #12619. (Please re-open if anyone has a different preference!)