Use the canonical org casing in the two README links

github.com/fastcomments/... 301s to github.com/FastComments/..., which
the docs site rewrites into a crawlable href and an external-link crawl
then flags as a redirect. The git+https install samples keep their
current casing - git resolves them fine and they are not links.

Author: winrid

README.md

@@ -17,7 +17,7 @@ Pin the tag rather than a branch so builds are deterministic. The same form work
 fastcomments @ git+https://github.com/fastcomments/fastcomments-python.git@v3.1.0
 ```
 
-Each tagged [GitHub Release](https://github.com/fastcomments/fastcomments-python/releases) also has a built wheel attached if you prefer to install a binary artifact directly.
+Each tagged [GitHub Release](https://github.com/FastComments/fastcomments-python/releases) also has a built wheel attached if you prefer to install a binary artifact directly.
 
 ### Library Contents
 
@@ -249,5 +249,5 @@ MIT
 ## Support
 
 - [Documentation](https://docs.fastcomments.com)
-- [GitHub Issues](https://github.com/fastcomments/fastcomments-python/issues)
+- [GitHub Issues](https://github.com/FastComments/fastcomments-python/issues)
 - [FastComments Support](https://fastcomments.com/auth/my-account/help)