Description:
As reported in issue ticket #6953 (Translations errors caused by
missing code block), there are several remaining lines of text directly
referencing file paths and/or OS commands where the commands and
their parameters get translated due to a lack of MarkDown code blocks.
Thanks to sebbu2 for reporting this issue.
Changes proposed:
- Encapsulate (enclose) CLi commands and folder paths in MD back ticks
- Remove MD bullet point indicators from the encapsulated lines
- Whitespace & grammar corrections:
- Normalize indentation, for the code blocks in particular
- Add missing MarkDown indent marker compatibility spacing
- Add blank line after H2 heading (MD codestyle standard)
- Grammar improvement: "allow reset" -> 'allows you to reset'
- Add readability comma to the same sentence
- Remove redundant blank line in the metadata section
Ticket closure or reference:
Closes#6953
Description:
The list of manual regsvr32.exe commands becomes translated in other
languages, to the extent that extra words appear among the commands.
This is an attempt to mitigate this behavior in the machine translation,
by adding a MarkDown code block around the list of commands.
Proposed changes:
- Add MD code block around the long list of regsvr32.exe commands
- Remove blank space characters at the end of each line (cosmetic)
issue ticket reference or closure:
Ref. #4800 (Spanish "translation" of commands)
Ref. #3569, #3570, #3571, #3572, #3574, #3575
( [LOC] Back-Translation "regsvr32.exe [...]" )
The correct order of the command `netsh winsock reset` is required.
The argument 'winsock' is the **context** and can not be rearranged.
In this context, 'reset' is the parameter to the context, not the context itself.
The correct command / context order is unchanged since Windows 2000.
Current order in the example is incorrect and needs to be amended:
- `netsh reset winsock` does not work, it returns an error message.
- `netsh winsock reset` is the correct order of context and parameter.
Closes#3157Closes#3193 (if not closed already)