Fix link to sqlite3 enable_shared_cache documentation

[orf]

Currently the link 404's, removing the slash fixes this.

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@orf

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

[erlend-aasland]

LGTM, thanks!

[erlend-aasland]

cc. @berkerpeksag @Fidget-Spinner

[orf]

FYI I've tried to sign the CLA three times - it's really unclear what your BPO username is if you've signed in via GitHub. I've tried several variations and even changed my username in BPO to match my GitHub name to no avail.

All that is to say, do I need to sign the CLA to get this tiny doc fix in?

[erlend-aasland]

FYI I've tried to sign the CLA three times - it's really unclear what your BPO username is if you've signed in via GitHub.

After you've logged in to BPO your username is shown in the menu to the left ("Hello, "). You can also view your BPO username as "Login Name" if you click on "Your Details".

[Fidget-Spinner]

Thanks for the PR!

FYI I've tried to sign the CLA three times - it's really unclear what your BPO username is if you've signed in via GitHub. I've tried several variations and even changed my username in BPO to match my GitHub name to no avail.

All that is to say, do I need to sign the CLA to get this tiny doc fix in?

AFAIK (and I might be completely wrong here, if so, sorry and please correct me), the CLA form checking and linking to your account is done manually by staff at the PSF. So you may have to give it some time if you just signed it yesterday. Additionally, from my hazy memory (I can't find this in the devguide right now), minor typo fixes do not necessarily need a CLA, only things that contain creative input. However, this is up to the core dev's discretion and not mine.

Edit: Ah great I found it: https://devguide.python.org/committing/?highlight=CLA#assessing-a-pull-request

[berkerpeksag]

LGTM. This is a minor fix so there is no need to wait for CLA, thank you!