Fixes #239 - Fixed section hierarchy and cleanup

Author: ralf401

advanced/macros.rst

@@ -63,6 +63,6 @@ To apply a macro to many tickets at the same time:
    When running a macro from the ticket view, Zammad may automatically open the
    next ticket (or close the current one, or just stay on it), depending on how
    the macro was set up.
-   
+
    When running it from the overviews page, Zammad will always stay on the
    overviews page.

advanced/suggested-workflows.rst

@@ -16,7 +16,7 @@ In these cases, there are three ways to assign the work to the right people:
 2. If you've done all you can on a ticket
    and it's now another agent's (or department's) responsibility,
    **reassign it** to a new owner (or group).
-3. If you just need another agent's input on something, you can **@mention** 
+3. If you just need another agent's input on something, you can **@mention**
    them. (And if *you* want to get notifications for *someone else's* ticket,
    use the **subscribe button**.)
 

advanced/text-modules.rst

@@ -18,7 +18,7 @@ module name or enter a keyword (if keywords are set).
 .. image :: /images/advanced/text-modules/using-text-modules.gif
 
 Text modules missing?
-^^^^^^^^^^^^^^^^^^^^^
+---------------------
 
 You noticed that some text modules don't always appear?
 
@@ -35,13 +35,13 @@ group.
 How do you know which groups go with which text modules? Ask your administrator!
 
 Text modules on ticket creation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+-------------------------------
 
 You can use text modules on ticket creation as well. On ticket creation,
 our :ref:`ticket_templates` might get handy too.
 
 Customizing text modules
-^^^^^^^^^^^^^^^^^^^^^^^^
+------------------------
 
 Administrators can learn more about customizing text modules
 :admin-docs:`here </manage/text-modules.html>`.

basics/find-ticket.rst

@@ -1,7 +1,7 @@
 Finding Tickets
 ===============
 
-If you plan to work on tickets, you’d better know how to find ’em first. 
+If you plan to work on tickets, you'd better know how to find them first.
 
 Read on to learn how to check for new tickets, and dig up old ones.
 

basics/service-ticket/create.rst

@@ -4,7 +4,7 @@ Creating a Ticket
 Zammad does its best to create tickets automatically
 when new customer issues come your way.
 But sometimes,
-there’s just no way for Zammad to know when an issue arrives –
+there's just no way for Zammad to know when an issue arrives –
 like when a customer calls on the phone.
 
 In these cases, Zammad needs your help to **create a new ticket**.
@@ -25,7 +25,7 @@ An agent can create three types of tickets:
 Filling Out the Form
 --------------------
 
-Here’s a quick run-down of each input field in the New Ticket form:
+Here's a quick run-down of each input field in the New Ticket form:
 
 Title
    The title of the ticket will be used as the **subject line**
@@ -38,12 +38,12 @@ Customer
    or else create a new customer.
 
    You may **not** assign a ticket to more than one customer.
-   
+
    .. figure:: /images/basics/service-ticket/create-customer-autocomplete.gif
       :alt: Customer autocomplete menu
       :align: center
 
-      Autocomplete can’t find customers by name.
+      Autocomplete can't find customers by name.
 
    .. tip:: **🖱️ UI Protip**
 

basics/service-ticket/settings/group.rst

@@ -6,7 +6,7 @@ that allows you to dictate *which agents are allowed to do what*
 to a given ticket.
 
 What?
-^^^^^
+-----
 
 Suppose your organization uses Zammad for both sales and customer support.
 You've got ten different agents spread across two teams,
@@ -26,7 +26,7 @@ If, instead, each agent were assigned to an appropriate group,
 then they'd only ever see the tickets that belong to their own group.
 
 Managing groups
-^^^^^^^^^^^^^^^
+---------------
 
 So how do I manage which team I'm on? You don't - that's the
 :admin-docs:`administrator's job </manage/groups/index.html>`.
@@ -43,7 +43,7 @@ your :doc:`user settings </extras/profile-and-settings>`:
    This user belongs to only one group (“Users”).
 
 So where do I come in?
-^^^^^^^^^^^^^^^^^^^^^^
+----------------------
 
 If you belong to more than one group,
 you may re-assign a ticket from one of your groups to another.

basics/service-ticket/settings/owner.rst

@@ -1,24 +1,24 @@
 Owner
 =====
 
-A ticket’s **owner** is simply
+A ticket's **owner** is simply
 *the agent that is currently responsible for it*.
 
 Whose job is it to assign tickets?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+----------------------------------
 
-It depends on your organization’s workflow,
+It depends on your organization's workflow,
 but in most cases,
 **you will assign tickets to yourself**
 when you choose an issue to work on
 from the pool of new tickets.
 
 In principle, any agent may assign a ticket to any other,
 as long as both have the required privileges
-for the ticket’s :doc:`group </basics/service-ticket/settings/group>`.
+for the ticket's :doc:`group </basics/service-ticket/settings/group>`.
 
 Why would I want to re-assign a ticket to someone else?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+-------------------------------------------------------
 
 Sometimes, complicated issues will require a ticket
 to be :ref:`passed back and forth between multiple agents <sharing-work>`

basics/service-ticket/settings/priority.rst

@@ -12,7 +12,7 @@ of *how urgent or important it is*.
    your tickets better.
 
 But what does it do, and how should I use it?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+---------------------------------------------
 
 Out of the box, **ticket priority doesn’t actually do anything**.
 However, Zammad administrators can set up all sorts of automated hooks

basics/service-ticket/settings/state.rst

@@ -17,17 +17,17 @@ and may be one of the following:
   (*i.e.,* hidden, but scheduled to reappear at a later date)
 
 State colors
-^^^^^^^^^^^^
+------------
 
 Zammad states are color-coded. This helps you to understanding the state of
-the ticket much faster in general – without having a look into details.
+the ticket much faster in general - without having a look into details.
 
 .. include:: /snippets/ticket-state-type-circles.rst
 
 .. _new-vs-open:
 
-What’s the difference between “new” and “open”?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+What's the difference between “new” and “open”?
+-----------------------------------------------
 
 States do more than just indicate progress: Zammad has a fine-grained time
 tracking feature (so-called
@@ -36,15 +36,15 @@ or SLAs) that uses state information to measure how long it takes for customers
 to get a response on a new ticket or get their issues resolved entirely.
 
 On a *new* ticket,
-the customer still hasn’t received her first response on the issue.
+the customer still hasn't received her first response on the issue.
 
 On an *open* ticket,
 the customer has received an initial response,
-but the issue still hasn’t been resolved.
+but the issue still hasn't been resolved.
 
 .. note:: ⏱️ Tickets in a *pending* state do not accumulate time toward their SLA limits.
 
    So, for instance, a ticket may be marked *pending reminder*
-   if it’s waiting on feedback from a third-party supplier
-   who’s out of town until next week.
+   if it's waiting on feedback from a third-party supplier
+   who's out of town until next week.
 

extras/two-factor-authentication.rst

@@ -59,7 +59,7 @@ key, etc.
    two-factor-authentication/authenticator-app-sign-in
 
 Trying Another Method
-~~~~~~~~~~~~~~~~~~~~~
+^^^^^^^^^^^^^^^^^^^^^
 
 In case you are having issued during sign-in with your preferred two-factor
 authentication method, you can switch to another one, provided you have set it

locale/user-docs.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad User Documentation pre-release\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-01-26 11:00+0100\n"
+"POT-Creation-Date: 2024-02-12 16:47+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1563,7 +1563,7 @@ msgid "Finding Tickets"
 msgstr ""
 
 #: ../basics/find-ticket.rst:4
-msgid "If you plan to work on tickets, you’d better know how to find ’em first."
+msgid "If you plan to work on tickets, you'd better know how to find them first."
 msgstr ""
 
 #: ../basics/find-ticket.rst:6
@@ -1702,7 +1702,7 @@ msgid "Creating a Ticket"
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:4
-msgid "Zammad does its best to create tickets automatically when new customer issues come your way. But sometimes, there’s just no way for Zammad to know when an issue arrives – like when a customer calls on the phone."
+msgid "Zammad does its best to create tickets automatically when new customer issues come your way. But sometimes, there's just no way for Zammad to know when an issue arrives – like when a customer calls on the phone."
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:10
@@ -1750,7 +1750,7 @@ msgid "Filling Out the Form"
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:28
-msgid "Here’s a quick run-down of each input field in the New Ticket form:"
+msgid "Here's a quick run-down of each input field in the New Ticket form:"
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:32
@@ -1779,7 +1779,7 @@ msgid "Customer autocomplete menu"
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:46
-msgid "Autocomplete can’t find customers by name."
+msgid "Autocomplete can't find customers by name."
 msgstr ""
 
 #: ../basics/service-ticket/create.rst:50
@@ -2195,19 +2195,19 @@ msgid "Owner"
 msgstr ""
 
 #: ../basics/service-ticket/settings/owner.rst:4
-msgid "A ticket’s **owner** is simply *the agent that is currently responsible for it*."
+msgid "A ticket's **owner** is simply *the agent that is currently responsible for it*."
 msgstr ""
 
 #: ../basics/service-ticket/settings/owner.rst:8
 msgid "Whose job is it to assign tickets?"
 msgstr ""
 
 #: ../basics/service-ticket/settings/owner.rst:10
-msgid "It depends on your organization’s workflow, but in most cases, **you will assign tickets to yourself** when you choose an issue to work on from the pool of new tickets."
+msgid "It depends on your organization's workflow, but in most cases, **you will assign tickets to yourself** when you choose an issue to work on from the pool of new tickets."
 msgstr ""
 
 #: ../basics/service-ticket/settings/owner.rst:16
-msgid "In principle, any agent may assign a ticket to any other, as long as both have the required privileges for the ticket’s :doc:`group </basics/service-ticket/settings/group>`."
+msgid "In principle, any agent may assign a ticket to any other, as long as both have the required privileges for the ticket's :doc:`group </basics/service-ticket/settings/group>`."
 msgstr ""
 
 #: ../basics/service-ticket/settings/owner.rst:21
@@ -2293,31 +2293,31 @@ msgid "State colors"
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:22
-msgid "Zammad states are color-coded. This helps you to understanding the state of the ticket much faster in general – without having a look into details."
+msgid "Zammad states are color-coded. This helps you to understanding the state of the ticket much faster in general - without having a look into details."
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:30
-msgid "What’s the difference between “new” and “open”?"
+msgid "What's the difference between “new” and “open”?"
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:32
 msgid "States do more than just indicate progress: Zammad has a fine-grained time tracking feature (so-called “:admin-docs:`service-level agreements </manage/slas/index.html>`”, or SLAs) that uses state information to measure how long it takes for customers to get a response on a new ticket or get their issues resolved entirely."
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:38
-msgid "On a *new* ticket, the customer still hasn’t received her first response on the issue."
+msgid "On a *new* ticket, the customer still hasn't received her first response on the issue."
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:41
-msgid "On an *open* ticket, the customer has received an initial response, but the issue still hasn’t been resolved."
+msgid "On an *open* ticket, the customer has received an initial response, but the issue still hasn't been resolved."
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:45
 msgid "⏱️ Tickets in a *pending* state do not accumulate time toward their SLA limits."
 msgstr ""
 
 #: ../basics/service-ticket/settings/state.rst:47
-msgid "So, for instance, a ticket may be marked *pending reminder* if it’s waiting on feedback from a third-party supplier who’s out of town until next week."
+msgid "So, for instance, a ticket may be marked *pending reminder* if it's waiting on feedback from a third-party supplier who's out of town until next week."
 msgstr ""
 
 #: ../basics/service-ticket/settings/tags.rst:2