Context

When checking the change log translation, I have found a wrong reference in an item of the change log. I have thus checked all the refs for 2022.2.

Link to issue number:

None
Follow-up of various issues.

Summary of the issue:

Some of the GitHub references in the change log were targetting wrong issue or PR.

Description of user facing changes

The references have been fixed in the change log document.

Description of development approach

Fixed the following references:

• Fixup of PR 13082: fix a misspell in DefaultAppArgs and no longer use globalVars.appArgs in a boolean context (#13386) #13386 replaced by Windows 10/11 Calculator: allow NVDA to announce more operations by suppressing only a limited number of keyboard commands #13383
• Revert "Update to py2exe 0.11.0.1 (#13066)" #13508 replaced by Windows 11 Design Elements Are Not Reported by NVDA When Mouse Tracking Is On #13506
• Fixup of PR 13082: fix a misspell in DefaultAppArgs and no longer use globalVars.appArgs in a boolean context (#13386) #13386 (bis) replaced by Windows 11 Notepad: status bar is not announced #13688

Also, I have replaced #13276 (Libre Office issue) by #13277 (associated PR) since the issue description is not related at all with the change for developers.

Testing strategy:

Manual test: Check each change log item in the change log generated by appVeyor in this PR.

Known issues with pull request:

I have also found some PR refs even if there are associated issues. The rule is usually to reference the issue when there is one. But I have not bothered to fix it since it is easy to find the issue when you have the PR.

Additional note:

• There have been 3 wrong references in the 2022.2 dev cycle. Maybe a checkof the ref should be added in NVAccess' protocol:
  • either check the ref just before merging a PR to master
  • or check all the refs (as I did in this PR) when you finalize the change log adding the intro text of the release

Change log entries:

None

Code Review Checklist:

• Pull Request description:
  • description is up to date
  • change log entries
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• API is compatible with existing add-ons.
• Documentation:
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English