Documentation fixes

docs/source/intro/quickstart.rst

@@ -50,7 +50,7 @@ Enjoy the API
 That was just a quick overview. In the next few pages of the introduction, we'll take a much more in-depth look of what
 we have just done above.
 
-If you are feeling eager to continue you can take a shortcut to :doc:`Invoking Methods <../start/invoking>` and come back
+If you are feeling eager to continue you can take a shortcut to :doc:`../start/invoking` and come back
 later to learn some more details.
 
 .. _community: https://t.me/Pyrogram

docs/source/topics/storage-engines.rst

@@ -74,8 +74,8 @@ In case you want to use an in-memory storage, but also want to keep access to th
     async with Client("my_account", in_memory=True) as app:
         print(await app.export_session_string())
 
-...and save the resulting string. You can use this string as session name the next time you want to login
-using the same session; the storage used will still be in-memory:
+...and save the resulting string. You can use this string by passing it as Client argument the next time you want to
+login using the same session; the storage used will still be in-memory:
 
 .. code-block:: python
 

docs/source/topics/synchronous.rst

@@ -1,7 +1,7 @@
 Synchronous Usage
 =================
 
-Pyrogram is an asynchronous framework and as such it is subject to the asynchronous rules. It can, however, run in
+Pyrogram is an asynchronous framework and as such is subject to the asynchronous rules. It can, however, run in
 synchronous mode (also known as non-asynchronous or sync/non-async for short). This mode exists mainly as a convenience
 way for invoking methods without the need of ``async``/``await`` keywords and the extra boilerplate, but **it's not the
 intended way to use the framework**.