One-line installer screen-shot replacement; clean-ups

Author: Adam Ciarciński

.DS_Store

@@ -0,0 +1 @@
+.DS_Store

.gitbook/assets/Screenshot 2024-10-30 at 12.08.43.png

@@ -27,26 +27,25 @@ Also, if core has a custom SSL CA to secure gRPC communication, [you need the CA
 ## Package Install
 
 1. On the [release page](https://github.com/DefGuard/gateway/releases) find and download a correct software package for your system (currently DEB, RPM and TXZ are available).
-2.  Install the package using relevant system tools:\
-    **Ubuntu/Debian:**
+2. Install the package using relevant system tools:
 
-    ```bash
-    sudo dpkg -i <path_to_deb_package>
-    ```
+   **Ubuntu/Debian:**
 
-    \
-    **Fedora/Red Hat Linux/SUSE:**
+   ```bash
+   sudo dpkg -i <path_to_deb_package>
+   ```
 
-    ```bash
-    sudo rpm -i <path_to_rpm_package>
-    ```
+   **Fedora/Red Hat Linux/SUSE:**
 
-    \
-    **FreeBSD:**
+   ```bash
+   sudo rpm -i <path_to_rpm_package>
+   ```
 
-    ```bash
-    pkg add <path_to_txz_package>
-    ```
+   **FreeBSD:**
+
+   ```bash
+   pkg add <path_to_txz_package>
+   ```
 3. Fill in the default configuration file (`/etc/defguard/gateway.toml`) with values corresponding to your Defguard installation (token and gRPC enpoint URL).
 4.  Enable and start the systemd service.
 
@@ -55,11 +54,11 @@ Also, if core has a custom SSL CA to secure gRPC communication, [you need the CA
     sudo systemctl start defguard-gateway.service
     ```
 
-## Docker-compose
+## Docker Compose
 
-To start your gateway using docker-compose:
+To start Defguard Gateway using [Docker Compose](https://docs.docker.com/compose/):
 
-1. We prepared a [git repository](https://github.com/DefGuard/deployment) with docker-compose configuration, clone it:
+1. We prepared a [git repository](https://github.com/DefGuard/deployment) with Docker Compose configuration, clone it:
 
 ```
 git clone --recursive https://github.com/DefGuard/deployment.git && cd deployment/gateway
@@ -71,20 +70,23 @@ git clone --recursive https://github.com/DefGuard/deployment.git && cd deploymen
 cp .env.template .env
 ```
 
-3. Finally, run the service with docker-compose:
+3. Finally, run the service with Docker Compose:
 
 ```
-docker-compose up
+docker compose up
 ```
 
-If everything went well, your Gateway should be connected to Defguard and you can start [adding new devices to your network](../../../features/setting-up-your-instance/features/wireguard/adding-wireguard-devices.md).
+If everything went well, Defguard Gateway should be connected to Defguard Core and you can start [adding new devices to your network](../../../features/setting-up-your-instance/features/wireguard/adding-wireguard-devices.md).
 
 ## OPNsense plugin
 
-To start your gateway as OPNsense plugin:
+[OPNsense®](https://opnsense.org) is an open source, feature rich firewall and routing platform, offering cutting-edge network protection.
+
+To start Defguard Gateway as OPNsense plugin:
 
 1. On the [release page](https://github.com/DefGuard/gateway/releases) find and download OPNsense package which will be named: \
-   `defguard-gateway_VERSION_x86_64-unknown-opnsense.pkg -`this package **includes the gateway as well as OPNSense plugin.**
+   `defguard-gateway_VERSION_x86_64-unknown-opnsense.pkg` - this package **includes Defguard Gateway as well as OPNSense plugin.**
+
 2. Install the package:
 
 ```bash
@@ -97,21 +99,21 @@ pkg add <path_to_txz_package>
 opnsense-patch
 ```
 
-4. Go to you OPNsense UI and navigate `VPN` -> `Defguard Gateway` .
+4. Go to you OPNsense UI and navigate to **VPN** > **Defguard Gateway**.
 
 <figure><img src="../../../.gitbook/assets/OPNSense Plugin.png" alt=""><figcaption></figcaption></figure>
 
-5. Fill form with appropriate values click `Save` then `Start/Restart`
+5. Fill out the form with appropriate values, click **Save**, and then click **Start/Restart**.
 
 {% hint style="info" %}
 You can find detailed description of all fields [here](../../../features/setting-up-your-instance/configuration.md#gateway-configuration).
 {% endhint %}
 
-If everything went well, your Gateway should be connected to Defguard and you can start [adding new devices to your network](../../../features/setting-up-your-instance/features/wireguard/adding-wireguard-devices.md).
+If everything went well, Defguard Gateway should be connected to Defguard Core and you can start [adding new devices to your network](../../../features/setting-up-your-instance/features/wireguard/adding-wireguard-devices.md).
 
 ## Binary Install
 
-1. Checkout Gateway releases [here](https://github.com/DefGuard/gateway/releases) and download compatible binary from Github page.
+1. Checkout Gateway releases [here](https://github.com/DefGuard/gateway/releases) and download compatible binary from GitHub page.
 2. Decompress and move to bin directory
 
 ```sh

.gitbook/assets/one-line-install.png

@@ -49,11 +49,11 @@ Before proceeding with the installation, ensure your system meets the following
 * If you have a **firewall**, we assume you have **open port 443** in order to expose both defguard and enrollment service, but also to automatically issue for these domains SSL Certificates. Port 444 (used for internal GRPC communication) **should not be exposed public.**
 * System clock is synchronized using Network Time Protocol (NTP). This is important for time-based one-time password (TOTP) codes.
 
-### Prequesities
+### Prerequisites
 
 #### PostgreSQL
 
-Defguard Core uses PostgreSQL database, so if you do not have installed and configured yet, you can do it in this section. For this tutorial we need to create **a user with superuser privileges and database**.
+Defguard Core uses [PostgreSQL](https://www.postgresql.org) database, so if you do not have installed and configured yet, you can do it in this section. For this tutorial we need to create **a user with superuser privileges and database**.
 
 First of all, install PostgreSQL package:
 

.gitignore

@@ -2,7 +2,7 @@
 icon: rocket
 ---
 
-# One-line install script
+# One-Line Installer
 
 {% hint style="info" %}
 The instance deployed by the script is meant to serve as a starting point and makes some tradeoffs to enable automated setup. Most importantly it assumes that your Web UI is available publicly (to generate SSL certificates with Caddy). In general it's not recommended for production and we strongly encourage you to customize this setup to work better within your own infrastructure.
@@ -12,17 +12,17 @@ To simplify the setup and enable automated deployment we prepared a script which
 
 Just by launching this one command there will be an interactive configuration and setup that will guide you step by step and deploy full defguard instance based on Docker Compose setup:
 
-<figure><img src="../../.gitbook/assets/Screenshot 2024-10-30 at 12.08.43.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/one-line-install.png" alt=""><figcaption></figcaption></figure>
 
 Just copy and paste this command and [secure the setup afterwards](one-line-install.md#securing-the-setup):
 
-### **Production release (most stable)**
+### Production Release (most stable)
 
 ```shell
 curl --proto '=https' --tlsv1.2 -sSf -L https://raw.githubusercontent.com/DefGuard/deployment/main/docker-compose/setup.sh -O && bash setup.sh
 ```
 
-### **Pre-release (latest alpha/beta/release candidate)**
+### Pre-release (latest alpha/beta/release candidate)
 
 ```bash
 curl --proto '=https' --tlsv1.2 -sSf -L https://raw.githubusercontent.com/DefGuard/deployment/main/docker-compose/setup.sh -O && bash setup.sh --pre-release
@@ -40,7 +40,7 @@ GATEWAY_IMAGE_TAG=pre-release
 Downgrading to the production release may not be trivial afterwards because of the changes made to the database during the upgrade.
 {% endhint %}
 
-### **Latest development builds**
+### Latest development builds
 
 ```bash
 curl --proto '=https' --tlsv1.2 -sSf -L https://raw.githubusercontent.com/DefGuard/deployment/main/docker-compose/setup.sh -O && bash setup.sh --dev