non newbie friendly the part about WinDbg

The actual debug information for "Debug unloading issues" **is extremely non newbie friendly.**

Please update with step by step instructions.

1. download WinDbg...

"it seems WinDbg does that automatically when breaking into .NET Core application"
what is this trying to tell me? automatically where? what?

just shows command? where was this run in what context, stated from where
```
".loadby sos coreclr"
```

This documentation was clearly written but someone who uses this on a daily basis,
and does not read well from some trying to come in new.

Please update so a complete newbie could follow.

Have Web project, im using AssemblyLoadContext, its not working as expected.... here are the steps.... to help
1. donwload WinDbg
explain what this is...
2. open ... terminal from x and run this command in the context of the location of your program...

I cant write it as i dnt know the steps and this doc doesn't help in that regard

#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: f3283764-f15a-fa5f-5106-6f294c780f7b
* Version Independent ID: b03cedce-9074-9686-0b31-045b2b4c862d
* Content: [How to use and debug assembly unloadability in .NET Core](https://docs.microsoft.com/en-us/dotnet/standard/assembly/unloadability)
* Content Source: [docs/standard/assembly/unloadability.md](https://github.com/dotnet/docs/blob/main/docs/standard/assembly/unloadability.md)
* Product: **dotnet-fundamentals**
* GitHub Login: @janvorli
* Microsoft Alias: **janvorli**