GITBOOK-438: change request with no subject merged in GitBook

Author: defguard-community

SUMMARY.md

@@ -123,7 +123,6 @@
 ## In depth
 
 * [Architecture Decision Records](in-depth/architecture-decision-records/README.md)
-  * [1.5](in-depth/architecture-decision-records/1.5.md)
   * [1.4](in-depth/architecture-decision-records/1.4.md)
   * [1.3](in-depth/architecture-decision-records/1.3.md)
   * [Pre-1.3](in-depth/architecture-decision-records/pre-1.3.md)

admin-and-features/access-control-list/README.md

@@ -63,7 +63,7 @@ Defguard does not track rule application status per location. In the event of ne
 Use the **Deploy pending changes** button to apply all the rules from **Pending Changes** section.
 
 {% hint style="info" %}
-### Batch rule application
+#### Batch rule application
 
 Defguard’s ACL functionality is designed to allow users to apply access control rules in batches. This approach minimizes the risk of transient network issues that could occur when deploying rules individually. By grouping changes and deploying them together, the system reduces the likelihood of connectivity hiccups or firewall disruptions.
 {% endhint %}
@@ -135,7 +135,7 @@ Access Control List (ACL) rules in Defguard are used to manage **who can access
 * At least one "allowed" source must always be specified - this defines who gets access.
 * Optionally, you can **exclude** specific users, groups, or devices using the "denied" section.
 * You can use this combination to create flexible rules, such as:\
-  &#xNAN;_Allow everyone in the “Remote Workers” group except a few individuals access specific office network._
+  \&#xNAN;_Allow everyone in the “Remote Workers” group except a few individuals access specific office network._
 
 This setup helps controlling access clearly and safely without worrying about lower-level network and firewall behavior.
 

admin-and-features/wireguard/create-your-vpn-network.md

@@ -28,12 +28,12 @@ It's a name that will be visible both on the UI, but also in the desktop client
 
 ### Gateway VPN IP addresses and masks
 
-By providing the VPN IPs/masks, you are configuring both: **the VPN internal networks and VPN server IPs**. Every gateway will bind to these addresses and Defguard will also generate and assign IP addresses for devices in this location from these networks. 
+By providing the VPN IPs/masks, you are configuring both: **the VPN internal networks and VPN server IPs**. Every gateway will bind to these addresses and Defguard will also generate and assign IP addresses for devices in this location from these networks.
 
 This field can contain multiple IP addresses (both IPv4 and IPv6), separated by a comma (e.g. `10.10.20.1/24,fc00::abcd:0:1/96`).
 
 {% hint style="info" %}
-## Dual-stack VPN networks
+### Dual-stack VPN networks
 
 Defguard supports dual-stack VPN networks, allowing simultaneous assignment of both IPv4 and IPv6 addresses to clients. Each VPN network can include multiple IPv4 and IPv6 subnets, and connected clients will automatically receive one address from each defined subnet. This enables seamless communication over both IP versions within a single VPN session.
 {% endhint %}

in-depth/architecture-decision-records/1.5.md

@@ -1,13 +1,10 @@
 ---
-description: >-
-  This module contains [Architecture Decision
-  Records](https://github.com/joelparkerhenderson/architecture-decision-record)
-  for Defguard.
+description: What are Defguard's Architecture Decision Records?
 ---
 
 # Architecture Decision Records
 
-Architecture Decision Records (ADRs) are concise documents that capture important architectural decisions made during the lifecycle of a software system.
+[Architecture Decision Records](https://github.com/joelparkerhenderson/architecture-decision-record) (ADRs) are concise documents that capture important architectural decisions made during the lifecycle of a software system.
 
 Each ADR focuses on a single decision, detailing the context, the decision itself, the alternatives considered, and the consequences of the chosen approach. They are critical for maintaining architectural clarity, especially in complex or long-lived projects where decisions can outlast the original developers.