docs: fix wrong service providers URL

[kaf-lamed-beyt]

closes #269

[SgtPooki]

@kaf-lamed-beyt this change does point me to the correct location but there are a lot of whitespace changes. Can you submit this PR without the unnecessary whitespace changes?

[kaf-lamed-beyt]

ah, let me do that now. my bad.

that must be prettier doing what it is not supposed to.

[rjan90]

@kaf-lamed-beyt the change in .gitignore I assume is unintended. Please revert that. Once that is done, the PR should be good to go.

[kaf-lamed-beyt]

hi @rjan90, it is intended.

my editor, Zed, does some formatting unnecessarily to markdown files, so i turned it off specifically for this project by adding a settings file a .zed/settings.json file, to turn off a couple of the formatting.

if i don't do that, this PR would include a couple of unnecessary whitespaces. see this

git should not track the file, that's why i included it in .gitignore, unless it is okay to have it in the repo, i can remove it from gitignore.

[SgtPooki]

@kaf-lamed-beyt you can always do git add -p to only stage piece of changes you want to commit before committing, or even do a hunk based staging via many GUI editors.

usually, a .gitignore should only contain the relevant files for a particular project and the standard tools of the maintainers.. while it's probably not harmful, having everyone that commits to a repo add their preferred tools to the .gitignore could result in a very long and unmanageable file where core maintainers may not be aware what/why certain lines exist.

It's usually best practice to just not stage & commit changes unless you know they are relevant to a particular repo

[SgtPooki]

@kaf-lamed-beyt also, you can do global git ignore files (and override that for individual repos/folders if you desire), or a local only ignore (no commit needed) for just this repo by doing:

> echo ".zed" >> .git/info/exclude

[kaf-lamed-beyt]

@kaf-lamed-beyt you can always do git add -p to only stage piece of changes you want to commit before committing, or even do a hunk based staging via many GUI editors.

usually, a .gitignore should only contain the relevant files for a particular project and the standard tools of the maintainers.. while it's probably not harmful, having everyone that commits to a repo add their preferred tools to the .gitignore could result in a very long and unmanageable file where core maintainers may not be aware what/why certain lines exist.

It's usually best practice to just not stage & commit changes unless you know they are relevant to a particular repo

oh, i get you now. thank you for the feedback, @SgtPooki

apologies for not responding on time. i see that you've already removed the line.

[kaf-lamed-beyt]

@kaf-lamed-beyt also, you can do global git ignore files (and override that for individual repos/folders if you desire), or a local only ignore (no commit needed) for just this repo by doing:

> echo ".zed" >> .git/info/exclude

thank you! i'll do this too.