Fix a few more issue styles with RTD (mostly lists/nested md)

readthedocs/extra/developing/telegram-api-in-other-languages.rst

@@ -13,18 +13,18 @@ C
 *
 
 Possibly the most well-known unofficial open source implementation out
-there by `**@vysheng** <https://github.com/vysheng>`__,
-```tgl`` <https://github.com/vysheng/tgl>`__, and its console client
-```telegram-cli`` <https://github.com/vysheng/tg>`__. Latest development
+there by `@vysheng <https://github.com/vysheng>`__,
+`tgl <https://github.com/vysheng/tgl>`__, and its console client
+`telegram-cli <https://github.com/vysheng/tg>`__. Latest development
 has been moved to `BitBucket <https://bitbucket.org/vysheng/tdcli>`__.
 
 JavaScript
 **********
 
-`**@zerobias** <https://github.com/zerobias>`__ is working on
-```telegram-mtproto`` <https://github.com/zerobias/telegram-mtproto>`__,
+`@zerobias <https://github.com/zerobias>`__ is working on
+`telegram-mtproto <https://github.com/zerobias/telegram-mtproto>`__,
 a work-in-progress JavaScript library installable via
-```npm`` <https://www.npmjs.com/>`__.
+`npm <https://www.npmjs.com/>`__.
 
 Kotlin
 ******
@@ -34,14 +34,14 @@ implementation written in Kotlin (the now
 `official <https://blog.jetbrains.com/kotlin/2017/05/kotlin-on-android-now-official/>`__
 language for
 `Android <https://developer.android.com/kotlin/index.html>`__) by
-`**@badoualy** <https://github.com/badoualy>`__, currently as a beta–
+`@badoualy <https://github.com/badoualy>`__, currently as a beta–
 yet working.
 
 PHP
 ***
 
 A PHP implementation is also available thanks to
-`**@danog** <https://github.com/danog>`__ and his
+`@danog <https://github.com/danog>`__ and his
 `MadelineProto <https://github.com/danog/MadelineProto>`__ project, with
 a very nice `online
 documentation <https://daniil.it/MadelineProto/API_docs/>`__ too.
@@ -51,7 +51,7 @@ Python
 
 A fairly new (as of the end of 2017) Telegram library written from the
 ground up in Python by
-`**@delivrance** <https://github.com/delivrance>`__ and his
+`@delivrance <https://github.com/delivrance>`__ and his
 `Pyrogram <https://github.com/pyrogram/pyrogram>`__ library! No hard
 feelings Dan and good luck dealing with some of your users ;)
 
@@ -59,6 +59,6 @@ Rust
 ****
 
 Yet another work-in-progress implementation, this time for Rust thanks
-to `**@JuanPotato** <https://github.com/JuanPotato>`__ under the fancy
+to `@JuanPotato <https://github.com/JuanPotato>`__ under the fancy
 name of `Vail <https://github.com/JuanPotato/Vail>`__. This one is very
 early still, but progress is being made at a steady rate.

readthedocs/extra/troubleshooting/rpc-errors.rst

@@ -17,11 +17,12 @@ something went wrong on Telegram's server). The most common are:
    said operation on a chat or channel. Try avoiding filters, i.e. when
    searching messages.
 
-The generic classes for different error codes are: \* ``InvalidDCError``
-(303), the request must be repeated on another DC. \*
-``BadRequestError`` (400), the request contained errors. \*
-``UnauthorizedError`` (401), the user is not authorized yet. \*
-``ForbiddenError`` (403), privacy violation error. \* ``NotFoundError``
-(404), make sure you're invoking ``Request``\ 's!
+The generic classes for different error codes are:
+
+- ``InvalidDCError`` (303), the request must be repeated on another DC.
+- ``BadRequestError`` (400), the request contained errors.
+- ``UnauthorizedError`` (401), the user is not authorized yet.
+- ``ForbiddenError`` (403), privacy violation error.
+- ``NotFoundError`` (404), make sure you're invoking ``Request``\ 's!
 
 If the error is not recognised, it will only be an ``RPCError``.

readthedocs/extra/wall-of-shame.rst

@@ -17,17 +17,19 @@ Shame <https://github.com/LonamiWebs/Telethon/issues?q=is%3Aissue+label%3ARTFM+i
 i.e. all issues labeled
 `"RTFM" <http://www.urbandictionary.com/define.php?term=RTFM>`__:
 
-> > **rtfm**
-> > Literally "Read The F\ **king Manual"; a term showing the
+       **rtfm**
+       Literally "Read The F--king Manual"; a term showing the
        frustration of being bothered with questions so trivial that the asker
        could have quickly figured out the answer on their own with minimal
        effort, usually by reading readily-available documents. People who
        say"RTFM!" might be considered rude, but the true rude ones are the
        annoying people who take absolutely no self-responibility and expect to
        have all the answers handed to them personally.
-> > *"Damn, that's the twelveth time that somebody posted this question
+
+       *"Damn, that's the twelveth time that somebody posted this question
        to the messageboard today! RTFM, already!"*
-> > **\ by Bill M. July 27, 2004*\*
+
+       *by Bill M. July 27, 2004*
 
 If you have indeed read the wiki, and have tried looking for the method,
 and yet you didn't find what you need, **that's fine**. Telegram's API