Update SS & correct api info

[RaneyDazed]

Please describe the purpose of this Pull Request.

Ensure correct API Key configuration for Sabnzbd connection in Radarr
and Sonarr settings, corrected sonarr category, added SS of both radarr and sonarr.

[RaneyDazed]

Might be a good idea to link to sab docs too? Since I removed the 2 lines that linked to it to reference the user/pass?

[RaneyDazed]

omg. I'll need to redo that. I think it renumbered the radarr page

[RaneyDazed]

Ok, should be set. Unless you want to link to (../apps/sabnzbd) somewhere

[chazlarson]

Why remove the link to the sab page? The edit is referring to an unidentified settings page, and I don't understand the point of explaining that an api key is used instead of a user/pass without saying why. Does user/pass not work?

[RaneyDazed]

My bad, I thought it would be nice to reflect the sabnzbd.md page under docs/apps, and just specify that they needed the API key. I certainly didn't mean to be rude or anything. Jeez.

[RaneyDazed]

I'll take different screen shots with user and pass

[chazlarson]

No, that's not the point. Api key is fine if that's what works. The issue was that the first pass told them to get the api key from some random "settings", without identifying which settings, while removing the link that answered that question. Sure, probably the Sabnzbd settings, but in all the rest of these we point directly to where the user finds this, so we should here as well.

It also added a line that said api key is preferred without explaining why; if api key is preferred, then it makes sense to point the user to where they can find it; my initial remark was that I didn't understand why that link was removed.

If user/pass should remain blank because api key is preferred or something, say that explicitly along with the preferred bit to avoid "the docs don't say how to use user/pass".

If either work, then perhaps say that, again to avoid "how do I?" questions.

[chazlarson]

There's no radarr page.