Remove obsolete TODO and make slow-down warning bold.

docs/source/rabbitmq-tutorial/7-publisher-confirms.rst

@@ -76,15 +76,11 @@ The handling of the exception usually consists in logging an error message and/o
 Different client libraries have different ways to synchronously deal with publisher confirms, so make sure to read
 carefully the documentation of the client you are using.
 
-This technique is very straightforward but also has a major drawback: it significantly slows down publishing, as the
+This technique is very straightforward but also has a major drawback: it **significantly slows down publishing**, as the
 confirmation of a message blocks the publishing of all subsequent messages.
 This approach is not going to deliver throughput of more than a few hundreds of published messages per second.
 Nevertheless, this can be good enough for some applications.
 
-..
-   TODO: Do we need to specify, that wait_for cancels the awaitables waiting for publisher confirmation when the timeout
-   occurs?
-
 Strategy #2: Publishing Messages in Batches
 +++++++++++++++++++++++++++++++++++++++++++