ac, afconvert, airshare: fix typos in French translation

[sebastiaanspeck]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):

[kbdharun]

LGTM, can you fix the spacing between description and symbols too, seems like we missed it while reviewing the previous PR.

[kbdharun]

Seems like the Codespell annotations issue for non-PR files still seems to exist 😵‍💫 (whatever fix we do it keeps coming back XD)

[sebastiaanspeck]

Seems like the Codespell annotations issue for non-PR files still seems to exist 😵‍💫 (whatever fix we do it keeps coming back XD)

Right now we only run on the English pages. This is correct, but since we ignore all translation folders, the changed files seems empty. If it is empty, it will run on all files (and so it will check the English pages).

• Only changed translated file
• Changed English and translated file

We could only trigger the codespell if ${{ steps.changed-files.outputs.all_changed_files}} is not empty (or '') OR like this:
934fa85 - to only run codespell on pages/*/*.md. We could also add contributing-guides/style-guide.md in addition.

• PR with only English pages
• PR with only translated page

Outdated

[sebastiaanspeck]

This PR is the reason why I should want to trigger more linter checks.. this would have been detected in the previous PR and it will help us to detect these small typo’s.

[kbdharun]

This PR is the reason why I should want to trigger more linter checks.. this would have been detected in the previous PR and it will help us to detect these small typo’s.

Agreed. For more info link script we can add maybe an argument like check and we can run it as part of the check PR script.

[sebastiaanspeck]

This PR is the reason why I should want to trigger more linter checks.. this would have been detected in the previous PR and it will help us to detect these small typo’s.

Agreed. For more info link script we can add maybe an argument like check and we can run it as part of the check PR script.

Something to put on the tracker issue 2023 #11146?

[kbdharun]

Something to put on the tracker issue 2023 #11146?

Yep

[leonvsc]

Typo fixes looks good to me!