fix build and ref warnings

8 files changed, 17 insertions, 13 deletions

diff --git a/docs/configexamples/ansible.rst b/docs/configexamples/ansible.rst
index 431ad8c3..fc243c44 100644
--- a/docs/configexamples/ansible.rst
+++ b/docs/configexamples/ansible.rst
@@ -119,7 +119,7 @@ Add the simple playbook with the tasks for each router:
 			true
 	
 Start the playbook:
-==================
+===================
 
 .. code-block:: none
 
@@ -158,7 +158,7 @@ Check the result on the vyos10 router:
 	set system name-server '8.8.8.8'
 
 The simple way without configuration of the hostname (one task for all routers):
-============================================================================
+================================================================================
 
 .. code-block:: none
 
diff --git a/docs/configuration/interfaces/openvpn.rst b/docs/configuration/interfaces/openvpn.rst
index 70161e1e..d92ac080 100644
--- a/docs/configuration/interfaces/openvpn.rst
+++ b/docs/configuration/interfaces/openvpn.rst
@@ -71,7 +71,7 @@ In both cases, we will use the following settings:
   dynamic IP for our remote router.
 
 Setting up certificates
------------------------
+=======================
 
 Setting up a full-blown PKI with a CA certificate would arguably defeat the purpose
 of site-to-site OpenVPN, since its main goal is supposed to be configuration simplicity,
@@ -129,7 +129,7 @@ Note: certificate names don't matter, we use 'openvpn-local' and 'openvpn-remote
 Repeat the procedure on the other router.
 
 Setting up OpenVPN
-------------------
+==================
 
 Local Configuration:
 
@@ -166,7 +166,7 @@ Remote Configuration:
                                                                                     on the local router
 
 Pre-shared keys
----------------
+===============
 
 Until VyOS 1.4, the only option for site-to-site OpenVPN without PKI was to use pre-shared keys.
 That option is still available but it is deprecated and will be removed in the future.
diff --git a/docs/configuration/protocols/ospf.rst b/docs/configuration/protocols/ospf.rst
index e360d86a..9891c77d 100644
--- a/docs/configuration/protocols/ospf.rst
+++ b/docs/configuration/protocols/ospf.rst
@@ -1204,7 +1204,7 @@ Interface Configuration
    synchronizing process of the router's database with all neighbors. The
    default value is 1 seconds. The interval range is 3 to 65535.
 
-.. _ospf:v3_redistribution_config:
+.. _ospf:v3_graceful_restart:
 
 Graceful Restart
 ----------------
@@ -1245,6 +1245,8 @@ Graceful Restart
 
    By default, it supports both planned and unplanned outages.
 
+.. _ospf:v3_redistribution_config:
+
 Redistribution Configuration
 ----------------------------
 
diff --git a/docs/configuration/protocols/pim.rst b/docs/configuration/protocols/pim.rst
index 1b97697d..2e881943 100644
--- a/docs/configuration/protocols/pim.rst
+++ b/docs/configuration/protocols/pim.rst
@@ -180,6 +180,8 @@ IGMP - Internet Group Management Protocol)
    Configure watermark warning generation for an IGMP group limit. Generates
    warning once the configured group limit is reached while adding new groups.
 
+.. _pim:igmp_interface_commands:
+
 Interface specific commands
 ===========================
 
@@ -202,7 +204,7 @@ Interface specific commands
    Use this command to configure in the selected interface the IGMP
    query response timeout value (10-250) in deciseconds. If a report is
    not returned in the specified time, it will be assumed the (S,G) or
-   (*,G) state :rfc:`7761#section-4.1` has timed out.
+   (\*,G) state :rfc:`7761#section-4.1` has timed out.
 
 .. cfgcmd:: set protocols pim interface <interface> igmp version <version-number>
 
diff --git a/docs/configuration/service/dhcp-relay.rst b/docs/configuration/service/dhcp-relay.rst
index e1fbe1d2..dc45d071 100644
--- a/docs/configuration/service/dhcp-relay.rst
+++ b/docs/configuration/service/dhcp-relay.rst
@@ -154,6 +154,8 @@ Configuration
 
    Disable dhcpv6-relay service.
 
+.. _dhcp_relay:v6_options:
+
 Options
 -------
 
diff --git a/docs/configuration/system/login.rst b/docs/configuration/system/login.rst
index 0cbcecde..98e05cdd 100644
--- a/docs/configuration/system/login.rst
+++ b/docs/configuration/system/login.rst
@@ -344,6 +344,8 @@ Configuration
 
    Source all connections to the TACACS servers from given VRF `<name>`.
 
+.. _login:tacacs_example:
+
 Configuration Example
 ---------------------
 
diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst
index 7a50bfb2..bd482cd9 100644
--- a/docs/configuration/vrf/index.rst
+++ b/docs/configuration/vrf/index.rst
@@ -282,6 +282,8 @@ Configuration
 VRF and NAT
 -----------
 
+.. _vrf:nat_configuration:
+
 Configuration
 ^^^^^^^^^^^^^
 
diff --git a/docs/quick-start.rst b/docs/quick-start.rst
index d20a39f9..c8bb3f04 100644
--- a/docs/quick-start.rst
+++ b/docs/quick-start.rst
@@ -128,12 +128,6 @@ interlinked chains for each `Netfilter hook
 <https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks>`_
 and allows for more granular control over the packet filtering process.
 
-.. note:: Documentation for most of the new firewall CLI can be found in
-   the :ref:`firewall` chapter.The legacy firewall is still available
-   for versions before ``1.4-rolling-202308040557`` and can be found in the
-   :ref:`firewall-legacy` chapter. The examples in this section use the
-   new configuration.
-
 The firewall begins with the base ``filter`` tables you define for each of the
 ``forward``, ``input``, and ``output`` Netfiter hooks. Each of these tables is
 populated with rules that are processed in order and can jump to other chains