Bias-free communication

[guardrex]

Fixes #33705

IMO, it's a good i-dear to do this every few years to fix problems. This was on my UE tracking issue for Blazor docs, but it's something that I usually do for the whole repo, given that it's just quick search filter stuff.

• https://learn.microsoft.com/en-us/style-guide/bias-free-communication
• https://learn.microsoft.com/en-us/style-guide/militaristic-language

Notes ...

• I left "attack" in place, but I preferred to use "cyberattacker" for "attacker" and "adversary."
• All of our "defense" terminology is related to cybersecurity threats, but I did change "defense" to "defense-in-depth cybersecurity" in a couple of spots.
• "guard" 👉 "safeguard"
• "hang" 👉 "stop responding"
• "attack surface area" 👉 "vulnerabilities"
• "locked down" 👉 "secured"
• BTW ... hitting "i.e."/"e.g." updates along the way ... not bias-free stuff, but we're not supposed to use these. Note that I omitted commas for short parenthetical phrases "(for example to {DO SOMETHING})." A comma in those cases didn't seem significant.
• One "master-detail" item changed to "primary-subordinate."

Not addressed

There are a few articles that are probably OK on he/his/him/her pronoun things because they refer to specific people with a usually obvious gender. Personally, I'd go with something like "user"/"another user" or "user"/"second user," but these are probably OK. Best to check tho in case anyone wants to update the John/Jane examples:

• https://learn.microsoft.com/en-us/aspnet/core/data/ef-mvc/concurrency?view=aspnetcore-8.0
• https://learn.microsoft.com/en-us/aspnet/core/data/ef-rp/concurrency?view=aspnetcore-8.0&tabs=visual-studio

[wadepickett]

Suggested change

	Use caution when providing users with the ability to download files from a server. Cyberattackers may execute [Denial of Service (DoS)](/windows-hardware/drivers/ifs/denial-of-service) attacks, [API exploitation attacks](https://developer.mozilla.org/docs/Web/HTML/Element/a#security_and_privacy), or attempt to compromise networks and servers in other ways.
	Use caution when providing users with the ability to download files from a server. Cyber attackers may execute [Denial of Service (DoS)](/windows-hardware/drivers/ifs/denial-of-service) attacks, [API exploitation attacks](https://developer.mozilla.org/docs/Web/HTML/Element/a#security_and_privacy), or attempt to compromise networks and servers in other ways.

[guardrex]

The guidelines call for one word, no hyphen/no space.

https://learn.microsoft.com/en-us/style-guide/militaristic-language

[wadepickett]

Very minor and feel free to refuse or accept: I think both "cyberattackers"and "cyber attackers" are used in the development community, but I think "cyber attackers" might be used more often.

[guardrex]

I don't think we have a choice given how explicit they are in the style manual. We've broken with them a bit here and there, but I think AP and Chicago are in agreement. My Chicago is buried at the moment tho ... in a box somewhere around here from the last move 😆.

[wadepickett]

Suggested change

	### Slow or nonresponding app (IIS)
	### Slow or non-responding app (IIS)

[guardrex]

Not per Chicago.

[wadepickett]

Very minor, take or leave: I think you can go either way technically, but I think non-responding might be a bit more common.

[guardrex]

"non-" is listed ...

https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/n/non

... and we defer to Chicago per MS guidelines ...

https://learn.microsoft.com/en-us/style-guide/grammar/grammar-and-parts-of-speech

[wadepickett]

Looks great!