Update README.md (#129)

README.md

@@ -16,11 +16,17 @@
 <a href='https://discord.socketify.dev/' target="_blank"><img alt='Discord' src='https://img.shields.io/discord/1042529276219641906?label=Discord'></a>
 </p>
 
+<div align="center">
+  <a href="https://docs.socketify.dev">Documentation</a>
+  <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
+  <a href="https://discord.socketify.dev/">Discord</a>
+  <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
+  <a href="https://github.com/cirospaciari/socketify.py/issues">Issues</a>
+  <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
+  <a href="https://github.com/cirospaciari/socketify.py/tree/main/examples">Examples</a>
+  <br />
+</div>
 
-## :bookmark_tabs: Documentation
-See the full docs in [docs.socketify.dev](https://docs.socketify.dev) or in [/docs/README.md](docs/README.md)
-
-Also take a look in the examples in [/examples](https://github.com/cirospaciari/socketify.py/tree/main/examples)
 ## 💡 Features
 
 - WebSocket with pub/sub support
@@ -204,16 +210,9 @@ Thank you [`Otavio Augusto`](https://github.com/middlebaws) to be the first spon
 ## :wrench: Forkers
 [![Forkers repo roster for @cirospaciari/socketify.py](https://reporoster.com/forks/dark/cirospaciari/socketify.py)](https://github.com/cirospaciari/socketify.py/network/members)
 
-
-## :question: socketify.py vs japronto
-
-People really want to compare with japronto, but this projects are not really comparable. Socketify is an active project and will be maintained over time with security updates and new features, japronto don't get any github updates since 2020 and don't get any src update since 2018, japronto don't support SSL, WebSockets, [`PyPy3`](https://www.pypy.org/), Windows or macOS Silicon, socketify will support Http3 and a lot more features. 
-
-And yes, we can be faster than japronto when all our features and goals are achieved, and we are probably faster than any current maintained solution out there.
-
 ## :grey_question: uvloop
 We don't use uvloop, because uvloop don't support Windows and PyPy3 at this moment, this can change in the future, but right now we want to implement our own libuv + asyncio solution, and a lot more.
 
 ## :dizzy: CFFI vs Cython vs HPy
-Cython performs really well on Python3 but really bad on PyPy3, CFFI are chosen for better support PyPy3 until we got our hands on an stable [`HPy`](https://hpyproject.org/) integration.
+Cython performs really well on Python3 but really bad on PyPy3, CFFI are chosen for better support PyPy3 until we got our hands on a stable [`HPy`](https://hpyproject.org/) integration.