(#794) Add Jargon Buster page

[pauby]

Description Of Changes

Adds the start of a Jargon Buster page.

Motivation and Context

Our documentation uses jargon and acronyms that we need to bust!

Testing

• I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

• Minor documentation fix (typos etc.).
• Major documentation change (refactoring, reformatting or adding documentation to existing page).
• New documentation page added.
• The change I have made should have a video added, and I have raised an issue for this.
  • Issue #

Change Checklist

• Requires a change to menu structure (top or left hand side)/
• Menu structure has been updated

Related Issue

Fixes #794

[pauby]

@gep13 @AdmiringWorm @vexx32 @corbob @st3phhays @Windos @ryanrichter94 @imm0rtalsupp0rt @JPRuskin I've tagged you all in this to review and suggest additions.

Note that this is not in any way complete. I want to get the obvious ones in here and we can update as we go along. Let me know of any, and their definitions and we can add them.

[corbob]

I'm not sure how I feel about using the term "jargon" in the title and the url. I'm thinking for people searching for it, what might they look for? At the very least, we should possibly include the term glossary somewhere.

[pauby]

I don't feel the word glossary is useful here. A glossary, to me, is a place where I can go and look up all word I don't know that are in the document I'm reading. This is only a page listing jargon and acronyms. It's not a glossary about what a network card is, or a terminal etc.

I feel that jargon buster (which is a commonly used phrase and many documents, technical and not, use them) is a good description of what this is.

[corbob]

learning-resources/index.md is already order level 60. Assuming we want this before "More Learning Resources" we should probably set this to 55.

[TheCakeIsNaOH]

If nupkg is here, nuspec would probably also be worthwhile to have.

[gep13]

It has been mentioned elsewhere, but capturing here as well, can we add CLE to the list?

Also, do we want the reciprocal entry for package? In the nupkg entry, we mention that this is a Chocolatey package, so in the package entry, we would mention that this is a file that ends with *.nupkg.

[gep13]

Suggested change

	Description: A reference guide on the jargon and acronyms used in our documentation.
	Description: A reference guide on the jargon and acronyms used in our documentation

None of our other Descriptions contain a . at the end. I noticed that there was an inconsistency in this area recently, and I made them the same. The overwhelming majority of our pages didn't have a ..

[vexx32]

Couple minor grammatical nits that read a bit funny to me, but otherwise I think this looks good so far :3

[vexx32]

Suggested change

	One of our goals for writing documentation, is clarity. As we update our documentation we strive to bring clarity to it. But this is a work in-progress. We recognize that jargon and acronyms can cause confusion, misunderstanding and act as a barrier for those who are getting started with our software.
	One of our goals for writing documentation, is clarity. As we update our documentation we strive to bring clarity to it, but this is a work in-progress. We recognize that jargon and acronyms can cause confusion, misunderstanding and act as a barrier for those who are getting started with our software.

[pauby]

The end of the sentence there was deliberate. As it emphasises the But in the next sentence.

[vexx32]

As far as I'm aware most style guides would say you shouldn't splice a sentence like that. Personally I don't think it helps the clarity for the reader, but it's not a huge issue either. 🤷‍♀️

[pauby]

If you can point me to a style guide, I'm happy to review it. I use LanguageTool (as I said) so I tend to rely on that as the source of truth.