From c1dd2ebb92ab52f061aa7afd235d2d05c84e587a Mon Sep 17 00:00:00 2001
From: Veronica Berglyd Olsen <1619840+vkbo@users.noreply.github.com>
Date: Tue, 24 Jun 2025 00:22:35 +0200
Subject: [PATCH] Fix typos and inconsistencies

---
 docs/source/usage/advanced_formatting.rst  |  6 +++---
 docs/source/usage/alignment_and_indent.rst | 18 +++++++++---------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/source/usage/advanced_formatting.rst b/docs/source/usage/advanced_formatting.rst
index 94bfec0f..556d6f1f 100644
--- a/docs/source/usage/advanced_formatting.rst
+++ b/docs/source/usage/advanced_formatting.rst
@@ -62,12 +62,12 @@ Forced Line Break
 -----------------
 
 Inserting ``[br]`` in the text will ensure a line break is always inserted in that place, even if
-you turn off **Preserve Hard Line breaks** in your **Manuscript Build Settings**.
+you turn off **Preserve Hard Line Breaks** in your manuscript build settings.
 
 You can add a manual line break after it too, for a better visual representation in the editor, but
 keep in mind that this line break is removed before the text is processed, so the text on either
-side will be considered as belonging to the same line. This can affect how alignment is treated.
-See :ref:`docs_usage_align_indent_forced` for more details.
+side of the ``[br]`` shortcode will be considered as belonging to the same line. This can affect
+how alignment is treated. See :ref:`docs_usage_align_indent_forced` for more details.
 
 
 .. _docs_usage_formatting_breaks:
diff --git a/docs/source/usage/alignment_and_indent.rst b/docs/source/usage/alignment_and_indent.rst
index dea1b171..60949b9a 100644
--- a/docs/source/usage/alignment_and_indent.rst
+++ b/docs/source/usage/alignment_and_indent.rst
@@ -69,9 +69,9 @@ precedence is:
 .. note::
 
    It is strongly recommended that you keep the **Preserve Hard Line Breaks** setting enabled in
-   your **Manuscript Build Settings**. This setting assumes all single line breaks in your text are
-   intended. Turning this off makes adding line breaks much more complicated, but it is still
-   possible. See :ref:`docs_usage_align_indent_forced`.
+   your manuscript build settings. This setting assumes all single line breaks in your text are
+   intended. Turning this off makes adding line breaks more complicated, but it is still possible.
+   See :ref:`docs_usage_align_indent_forced`.
 
 
 Alignment with First Line Indent
@@ -98,13 +98,13 @@ The following text will always be aligned against the left margin:
 Alignment with Forced Line Breaks
 =================================
 
-If you turn off **Preserve Hard Line Breaks** in **Manuscript Build Settings**, you can still force
-line breaks in paragraphs using the ``[br]`` shortcode. For clarity in the text, you can add a line
-break after it as well. It doesn't result in two line breaks.
+If you turn off **Preserve Hard Line Breaks** in your manuscript build settings, you can still
+force line breaks in paragraphs using the ``[br]`` shortcode. For clarity in the text, you can add
+a line break after it as well. It doesn't result in two line breaks.
 
-Keep in mind that when the text is processed, these lines on either side of a ``[br]`` shortcode
-are combined, and a trailing hard line break is *ignored*. This means that when such a paragraph is
-processed, these line breaks count as the same line. This affects hiw alignment tags are handled.
+Keep in mind that when the text is processed, the lines on either side of a ``[br]`` shortcode are
+combined, and any trailing hard line break is *ignored*. This means that when such a paragraph is
+processed, these line breaks count as the same line. This affects how alignment tags are handled.
 For instance, this text becomes centred instead of left aligned.
 
 .. code-block:: md