Period after bold

CONTRIBUTING.rst

@@ -165,31 +165,31 @@ Bugs can always be described to the `mailing-list`_, but the best
 way to report an issue and to ensure a timely response is to use the
 issue tracker.
 
-1) **Create a GitHub account.**
+1) **Create a GitHub account**.
 
 You need to `create a GitHub account`_ to be able to create new issues
 and participate in the discussion.
 
 .. _`create a GitHub account`: https://github.com/signup/free
 
-2) **Determine if your bug is really a bug.**
+2) **Determine if your bug is really a bug**.
 
 You shouldn't file a bug if you're requesting support. For that you can use
 the `mailing-list`_, or `irc-channel`_.
 
-3) **Make sure your bug hasn't already been reported.**
+3) **Make sure your bug hasn't already been reported**.
 
 Search through the appropriate Issue tracker. If a bug like yours was found,
 check if you have new information that could be reported to help
 the developers fix the bug.
 
-4) **Check if you're using the latest version.**
+4) **Check if you're using the latest version**.
 
 A bug could be fixed by some other improvements and fixes - it might not have an
 existing report in the bug tracker. Make sure you're using the latest releases of
 celery, billiard, kombu, amqp and vine.
 
-5) **Collect information about the bug.**
+5) **Collect information about the bug**.
 
 To have the best chance of having a bug fixed, we need to be able to easily
 reproduce the conditions that caused it. Most of the time this information
@@ -224,7 +224,7 @@ spelling or other errors on the website/docs/code.
         confidential information like API tokens and authentication
         credentials.
 
-6) **Submit the bug.**
+6) **Submit the bug**.
 
 By default `GitHub`_ will email you to let you know when new comments have
 been made on your bug. In the event you've turned this feature off, you

docs/contributing.rst

@@ -165,31 +165,31 @@ Bugs can always be described to the :ref:`mailing-list`, but the best
 way to report an issue and to ensure a timely response is to use the
 issue tracker.
 
-1) **Create a GitHub account.**
+1) **Create a GitHub account**.
 
 You need to `create a GitHub account`_ to be able to create new issues
 and participate in the discussion.
 
 .. _`create a GitHub account`: https://github.com/signup/free
 
-2) **Determine if your bug is really a bug.**
+2) **Determine if your bug is really a bug**.
 
 You shouldn't file a bug if you're requesting support. For that you can use
 the :ref:`mailing-list`, or :ref:`irc-channel`.
 
-3) **Make sure your bug hasn't already been reported.**
+3) **Make sure your bug hasn't already been reported**.
 
 Search through the appropriate Issue tracker. If a bug like yours was found,
 check if you have new information that could be reported to help
 the developers fix the bug.
 
-4) **Check if you're using the latest version.**
+4) **Check if you're using the latest version**.
 
 A bug could be fixed by some other improvements and fixes - it might not have an
 existing report in the bug tracker. Make sure you're using the latest releases of
 celery, billiard, kombu, amqp and vine.
 
-5) **Collect information about the bug.**
+5) **Collect information about the bug**.
 
 To have the best chance of having a bug fixed, we need to be able to easily
 reproduce the conditions that caused it. Most of the time this information
@@ -225,7 +225,7 @@ spelling or other errors on the website/docs/code.
         confidential information like API tokens and authentication
         credentials.
 
-6) **Submit the bug.**
+6) **Submit the bug**.
 
 By default `GitHub`_ will email you to let you know when new comments have
 been made on your bug. In the event you've turned this feature off, you

docs/whatsnew-4.0.rst

@@ -213,7 +213,7 @@ attempting to use them will raise an exception:
     persistent result backend for multi-consumer results.
 
 
-**Now to the good news...**
+**Now to the good news**...
 
 New Task Message Protocol
 -------------------------