[PATCH b4 11/21] docs: move sentence-ending dots from within the last quoted string to outside

[Quentin Schulz <foss+kernel@0leil.net>]

From: Quentin Schulz <quentin.schulz@cherry.de>

These dots aren't meant to be part of the quoted string but as
sentence-ending dots so let's fix that.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 docs/config.rst           | 6 +++---
 docs/contributor/prep.rst | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/config.rst b/docs/config.rst
index 6b33c33..aff0ec3 100644
--- a/docs/config.rst
+++ b/docs/config.rst
@@ -60,7 +60,7 @@ These options control many of the core features of b4.
 
 ``b4.linktrailermask`` (v0.13+)
   Overrides the format of the ``Link:`` trailer, in case you want to
-  call it something other than "Link." For example, some projects
+  call it something other than "Link". For example, some projects
   use "Message-ID" trailers instead::
 
       linktrailermask = Message-ID: <%s>
@@ -85,7 +85,7 @@ These options control many of the core features of b4.
 
 ``b4.save-maildirs``
   The "mbox" file format is actually several incompatible standards,
-  such as "mboxo" vs. "mboxrd." Setting this option can avoid potential
+  such as "mboxo" vs. "mboxrd". Setting this option can avoid potential
   problems by saving retrieved threads as Maildirs.
 
   Default: ``no``
@@ -116,7 +116,7 @@ These options control many of the core features of b4.
       Signed-off-by: Your Name <your.name@example.com>
 
   Your custody section is beneath "Ezri Submaintainer," so the only
-  trailers considered for reordering are "Link" and "Tested-by." Your
+  trailers considered for reordering are "Link" and "Tested-by". Your
   own Signed-off-by trailer is always at the bottom of your own custody
   section.
 
diff --git a/docs/contributor/prep.rst b/docs/contributor/prep.rst
index 6e90b10..9c27b64 100644
--- a/docs/contributor/prep.rst
+++ b/docs/contributor/prep.rst
@@ -126,7 +126,7 @@ Enrolling an existing branch
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 If you've already started working on a set of commits without first
 running ``b4 prep -n``, you can enroll your existing branch to make it
-"prep-tracked."
+"prep-tracked".
 
 For example, if you have a branch called ``my-topical-branch`` that was
 forked from ``master``, you can enroll it with b4::

-- 
2.52.0