diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 71cc417c..9b55543c 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -12,6 +12,7 @@ A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,8 +25,9 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. Arch Linux on Wayland]
- - Version [e.g. 1.2.2]
+
+- OS: [e.g. Arch Linux on Wayland]
+- Version [e.g. 1.2.2]
 
 **Additional context**
 Add any other context about the problem here.
diff --git a/README.md b/README.md
index c955846d..dea074ff 100644
--- a/README.md
+++ b/README.md
@@ -1,25 +1,40 @@
 # Bussin Web X
 
 An alternative to the World Wide Web (`http(s)://`), with:
-- its own **custom browser** written in Rust with [GTK](https://gtk.org/),
+
+- its own **custom browser** written in [Rust](https://www.rust-lang.org/) with [GTK](https://gtk.org/),
 - custom HTML, CSS and ***Lua*** engine (yup, **no javascript! 🎉**),
 - custom **DNS** allowing Top-Level domains such as `rizz`, `sigma`, `lol`, `dev`, etc,
 - and **search engine** at `buss://dingle.it`.
 
 ![Preview of buss://register.it, the frontend for registering domains](.github_assets/image.png)
 
-# File structure
-- `/napture` - The source code for the **browser** Bussin Napture, used to view buss:// sites.
-- `/dns` - The source code for the **DNS** (Domain Name System), used for the API at `https://api.buss.lol`
-- `/dingle` - The source code for the official **search engine** (API) of Web X. For the frontend, check [dingle frontend repo](https://github.com/face-hh/dingle-frontend)
+## File structure
+
+- `/docs` - The source MarkDown for the **official documentation website**, currently hosted at [https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website). Has both user manuals for the official browser & guides and docs for developers who want to create websites for Web X.
+- `/napture` - The source code for the **browser**, "Bussin Napture", used to view buss:// sites.
+- `/dns` - The source code for the **DNS** (Domain Name System), used for the API at `https://api.buss.lol`.
+- `/dingle` - The source code for the official **search engine** of Web X. This is for the API only, for the frontend go check the [Dingle frontend repo](https://github.com/face-hh/dingle-frontend)
 - [registrar](https://github.com/face-hh/webx-registrar) - The source code for `buss://register.it`, frontend for `https://api.buss.lol` made for Bussin Web X. This can also serve as an example for how buss:// sites are made.
 
-# Download and Install
-## Arch Linux
-- `yay -S napture`, it's available on AUR.
-## Nix[OS]
+## Documentation
+
+> [!NOTE]
+> Note: This is just a summary, full docs can be found at the [WebX official documentation](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website)
+
+### Download and Install
+
+#### Install for Linux
+
+- For now, you have to download [Rust](https://www.rust-lang.org/tools/install). Then, you just need to open `install-linux.sh` in the `napture` folder as an executable (if you can't execute it, first do `sudo chmod +x ./install-linux.sh`, then you should be able to install).
+
+#### Install for Arch Linux
+
+- Run `yay -S napture`, it's available on AUR.
+
+#### Install for Nix[OS]
 
-**Flakes**: The repository provides a flake which exposes an overlay providing the webx package, so you could just add the input in your flake.nix file
+- **Flakes**: The repository provides a flake which exposes an overlay providing the webx package, so you could just add the input in your flake.nix file
 
 ```nix
 {
@@ -51,20 +66,24 @@ home.packages = with pkgs; [
 
 Then you could just launch it using `webx` in your terminal.
 
-## Linux
-- For now, you have to download [Rust](https://www.rust-lang.org/tools/install). Then, you just need to open `install-linux.sh` in the `napture` folder as an executable (if you can't execute it, first do `sudo chmod +x ./install-linux.sh`, then you should be able to install).
-## macOS
+#### Install for macOS
+
 - For now, you have to download [Rust](https://www.rust-lang.org/tools/install) and [Homebrew](https://brew.sh). Then, you just need to open `install-macos.sh` in the `napture` folder as an executable (if you can't execute it, first do `chmod +x ./install-macos.sh`, then you should be able to install).
-## Windows
+
+#### Install for Windows
+
 - Install the executable from the release tab. It's a self-extractor with WinRAR because it has a lot of DLLs.
 
-# Download and Compile
-## Linux
-Install [Rust](https://www.rust-lang.org/tools/install) if you haven't already.
-It should work by default, but if you're getting errors such as "missing PC files", you should Google it. Most likely you just have to install a library
+### Download and Compile
+
+#### Compile for Linux
+
+- Install [Rust](https://www.rust-lang.org/tools/install) if you haven't already. It should work by default, but if you're getting errors such as "missing PC files", you should Google it. Most likely you just have to install a library
+
+#### Compile for Windows
+
+> Welcome to Gaming OS 🙂
 
-## Windows
-Welcome to Gaming OS 🙂
 1. Download [Rust](https://www.rust-lang.org/tools/install)
 2. Download GNU target: `rustup toolchain install stable-gnu && rustup default stable-gnu`
 3. Download [MSYS32](https://www.msys2.org/)
@@ -75,19 +94,26 @@ Welcome to Gaming OS 🙂
 8. Select `Path` -> Click on `Edit` -> Add the following three entries: `C:\msys64\mingw64\include`, `C:\msys64\mingw64\bin`, and `C:\msys64\mingw64\lib`.
 9. Open a terminal in the folder with `napture/`, run `cargo run`.
 
-## MacOS (Apple Silicon)
+#### Compile for macOS (Apple Silicon)
+
 1. Install [Rust](https://www.rust-lang.org/tools/install)
 2. Install [Homebrew](https://brew.sh/)
-3. Install PKG_CONFIG_PATH and ensure it's set in your path
+3. Clone the repo
+
+```bash
+git clone https://github.com/face-hh/webx
+```
+
+4. Install PKG_CONFIG_PATH and ensure it's set in your path
 
 ```bash
 brew install pkg-config
 which pkg-config
 ```
 
-3.1. Should return something like `/opt/homebrew/bin/pkg-config`. If it doesn't, add it to your path.
+4.1. Should return something like `/opt/homebrew/bin/pkg-config`. If it doesn't, add it to your path.
 
-4. Install GTK and Necessary Libraries
+5. Install GTK and the necessary Libraries
 
 ```bash
 brew install glib
@@ -109,7 +135,7 @@ brew --prefix libadwaita
 brew --prefix lua@5.4
 ```
 
-4.1 Validate if the libraries are installed adequately and set in PKG_CONFIG_PATH, command below should return the path to the libraries without any errors.
+5.1 Validate if the libraries are installed adequately and set in PKG_CONFIG_PATH, command below should return the path to the libraries without any errors.
 
 ```bash
 pkg-config --libs --cflags glib-2.0
@@ -122,7 +148,7 @@ pkg-config --libs --cflags libadwaita-1
 pkg-config --libs --cflags lua-5.4
 ```
 
-5. Run `cargo run` in the `napture/` directory.
+6. Run `cargo run` in the `napture/` directory.
 
 ```bash
 cd napture
@@ -132,10 +158,12 @@ cargo build
 cargo run
 ```
 
-# Register website
-Please follow [How to code a Buss site](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website/) for a better visual guide.
+## Website registering
+
+> [!NOTE]
+> Again: This is just a summary, full docs can be found at the [WebX official documentation](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website). **Please head to the docs for a better and more visual guide.**
 
-So you wish to publish a website to Web X? Great! Let's go through the rules:
+So, you wish to publish a website to Web X? Great! Let's go through the rules:
 
 1. If your website contains Not Safe For Work material of any kind, it will be removed.
 2. If your website contains frequent racial slurs, references made in bad faith to tragic events, racism towards other races, or anything of that kind, it will be removed.
@@ -148,7 +176,7 @@ So you wish to publish a website to Web X? Great! Let's go through the rules:
 9. If your website is involved in fradulent activities, scams, or deceptive practices, it will be removed.
 10. If your website contains content that encourages harmful behavior, including self-harm, suicide, substance abuse, or dangerous challanges, it will be removed.
 
-By publishing content to this platform ("Bussin Napture"/"Bussin Web X"), you agree to comply with all rules and regulations set forth by the administrators. The administrators reserve the right to interpret and enforce these rules at their discretion. To report websites that are not following the listed rules, please contact `FaceDev` on either [Twitter](https://twitter.com/facedevstuff) or [Discord](https://discord.gg/cNwWvdWj42).
+**By publishing content to this platform ("Bussin Napture" / "Bussin Web X"), you agree to comply with all rules and regulations set forth by the administrators. The administrators reserve the right to interpret and enforce these rules at their discretion. To report websites that are not following the listed rules, please contact `FaceDev` on either [Twitter](https://twitter.com/facedevstuff) or [Discord](https://discord.gg/cNwWvdWj42).**
 
 Now, to register a website, navigate to `buss://register.it` **through Bussin Napture**.
 
@@ -156,31 +184,42 @@ You will see this interface.
 ![Preview of buss://register.it, the frontend for registering domains](.github_assets/image.png)
 
 What you need is the **Publish** section.
+
 - for the domain name, choose whatever you want. (example: `duckduckgo`)
 - for the TLD, choose one displayed above the `Result will appear...` label. (example: `rizz`)
 - for the IP, you can either use:
-   - an IP that serves `/index.html` on port 80
-   - a GitHub repository that has `index.html`, **outside any folder**. (example: [registrar](https://github.com/face-hh/webx-registrar)), ***with the `main` default branch***.
+  - an IP that serves `/index.html` on port 80
+  - a GitHub repository that has `index.html`, **outside any folder**. (example: [registrar](https://github.com/face-hh/webx-registrar)), ***with the `main` default branch***.
+
+Don't worry! The IP doesn't have to be valid, allowing you to register a domain and save it for later!
 
-Don't worry! The IP doesn't have to be valid, and you can save the domain for later!
+**WARNING**: After creating the domain, you'll be shown a **secret key**. Please make sure to save it as you will need it to Update/Delete your domain. With your secret key you can, for example, edit the IP of your website.
 
-**WARNING**: After creating the domain, you'll be shown a **secret key**. Please make sure to save it as you will need it to Update/Delete your domain.
+## Running a website locally
 
-# Run website locally
 Bussin Napture fetches `index.html` at whatever path you give it. For example, if you enter `http://localhost:3000`, Napture will fetch `http://localhost:3000/index.html`. From the index.html, if you have further `<link>` or `<script>` imports, they will be fetched at `http://localhost:3000/file.(css|lua)`.
 
 1. To locally test a website, you can use something like [Python](https://www.python.org/):
+
 ```bash
 python -m http.server 3000
 ```
+
 2. CLI support with `./napture file:///home/path/to/folder`.
 3. Enter `file:///home/path/to/folder` in the search bar.
 
-# HTML guide
+## HTML++ guide
+
+> "HTML++" = WebX HTML
+
 The supported tags are: `head`, `title`, `link`, `meta`, `script`, `h1`-`h6`, `div`, `p`, `ul`, `ol`, `li`, `div`, `button`, `hr`, `img`, `input`, `textarea`, `button`, `select`, `option`. Keep in mind their syntax may be different if you're already familiar with HTML5 (i.e. `link` is used for the tab icon). Please check [registrar](https://github.com/face-hh/webx-registrar) or `/napture/test/index.html` for examples.
 
-# CSS guide
+## CSS 3.25 guide
+
+> "CSS 3.25" = WebX CSS
+
 The supported properties are:
+
 - `border-color`
 - `border-width`
 - `border-style`
@@ -209,8 +248,12 @@ The supported properties are:
 
 Properties whose value type wasn't specified are either measured in `px`, or are colors (`#fff`, `red`, etc.)
 
-# Lua guide
-For those coming from the traditional web...
+## Lua guide
+
+> "Lua" = WebX JS = Luau
+
+In a nutshell for those coming from the traditional web:
+
 ```diff
 - 1. const test = document.querySelector(".classExample");
 - 2. test.textContent = "abc";
@@ -226,8 +269,6 @@ For those coming from the traditional web...
 + 6. test.on_submit(function())
 ```
 
-I believe you'd get a better understand if you explored the [registrar](https://github.com/face-hh/webx-registrar) repository's `script.lua`.
-
-NOTE: Bussin Napture doesn't support `buss://` redirects yet. They will be added in the official release.
+You'll probably get a better understanding if you explore the [registrar](https://github.com/face-hh/webx-registrar) repository's `script.lua`.
 
-Made by FaceDev with pure utter hatred and undesire :D
\ No newline at end of file
+*Made by FaceDev with pure utter hatred and undesire :D*
diff --git a/dingle/README.md b/dingle/README.md
index 367d967c..9f3bd0ce 100644
--- a/dingle/README.md
+++ b/dingle/README.md
@@ -1,3 +1,3 @@
 # Dingle.it
 
-This folder contains the source code for the API behind buss://dingle.it, the official search engine of Bussin Web X.
\ No newline at end of file
+This folder contains the source code for the API behind buss://dingle.it, the official search engine of Bussin Web X.
diff --git a/dns/README.md b/dns/README.md
index dd121b8a..66d01c22 100644
--- a/dns/README.md
+++ b/dns/README.md
@@ -21,15 +21,21 @@ Returns a simple message with the available endpoints and rate limits.
 
 **Response:**
 
-```
-Hello, world! The available endpoints are:
-GET /domains,
-GET /domain/{name}/{tld},
-POST /domain,
-PUT /domain/{key},
-DELETE /domain/{key},
-GET /tlds.
-Ratelimits are as follows: 10 requests per 60s.
+```txt
+webxDNS v0.3.0!
+
+The available endpoints are:
+
+ - [GET] /domains
+ - [GET] /domain/{name}/{tld}
+ - [POST] /domain
+ - [PUT] /domain/{key}
+ - [DELETE] /domain/{key}
+ - [GET] /tlds
+
+Ratelimits are as follows: 5 requests per 10 minutes on `[POST] /domain`.
+
+Code link: https://github.com/face-hh/webx/tree/master/dns
 ```
 
 ### POST /domain
@@ -43,25 +49,28 @@ Creates a new domain entry.
 - Headers:
   - `Content-Type: application/json`
 - Body:
+
   ```json
   {
-  	"tld": "example_tld",
-  	"ip": "example_ip",
-  	"name": "example_name"
+   "tld": "example_tld",
+   "ip": "example_ip",
+   "name": "example_name"
   }
   ```
 
 **Response:**
 
 - `200 OK` if the domain is successfully created.
+
   ```json
   {
-  	"tld": "example_tld",
-  	"ip": "example_ip",
-  	"name": "example_name",
-  	"secret_key": "generated_secret_key"
+   "tld": "example_tld",
+   "ip": "example_ip",
+   "name": "example_name",
+   "secret_key": "generated_secret_key"
   }
   ```
+
 - `400 Bad Request` if the request body is invalid, the TLD is non-existent, the name is too long (24 chars), or the domain is offensive.
 - `409 Conflict` if the domain already exists.
 
@@ -80,13 +89,15 @@ Fetches a domain entry by name and TLD.
 **Response:**
 
 - `200 OK` if the domain is found.
+
   ```json
   {
-  	"tld": "example_tld",
-  	"name": "example_name",
-  	"ip": "example_ip"
+   "tld": "example_tld",
+   "name": "example_name",
+   "ip": "example_ip"
   }
   ```
+
 - `404 Not Found` if the domain is not found.
 
 ### PUT /domain/:key
@@ -102,20 +113,23 @@ Updates the IP address of a domain entry using its secret key.
 - Headers:
   - `Content-Type: application/json`
 - Body:
+
   ```json
   {
-  	"ip": "new_ip_address"
+   "ip": "new_ip_address"
   }
   ```
 
 **Response:**
 
 - `200 OK` if the IP address is successfully updated.
+
   ```json
   {
-  	"ip": "new_ip_address"
+   "ip": "new_ip_address"
   }
   ```
+
 - `404 Not Found` if the domain is not found.
 
 ### DELETE /domain/:key
@@ -146,6 +160,7 @@ Fetches all domain entries.
 **Response:**
 
 - `200 OK` with a list of domains.
+
   ```json
   [
     {
@@ -169,6 +184,7 @@ Fetches the list of allowed top-level domains.
 **Response:**
 
 - `200 OK` with a list of TLDs.
+
   ```json
   ["example_tld1", "example_tld2", ...]
   ```
diff --git a/docs/README.md b/docs/README.md
index c1dead5b..972d3671 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -4,14 +4,30 @@ description: An alternative to the World Wide Web
 
 # Welcome to WebX
 
+## Quick jump
+
+[Keybinds](for-users/advanced-user-manual.md#keybinds)
+
+[WebX API reference](for-developers/api-reference.md#api-reference)
+
 ## Manuals
 
 [User manual](for-users/basic-user-manual.md#first-thing-first-install-napture)
 
-[Developer manual ](for-developers/getting-started.md#webx-developer-guide)
+[Developer manual](for-developers/getting-started.md#webx-developer-guide)
 
-## Quick jump
+## Full table of contents
 
-[Keybinds](for-users/advanced-user-manual.md#keybinds)
+### For users
 
-[WebX API reference](for-developers/api-reference.md#api-reference)
+* [User manual](for-users/basic-user-manual.md)
+* [Advanced user manual](for-users/advanced-user-manual.md)
+
+### For developers
+
+* [Getting started](for-developers/getting-started.md)
+  * [HTML++](for-developers/html++.md)
+  * [CSS 3.25](for-developers/css-3.25.md)
+  * [Lua](for-developers/luau.md)
+* [Publishing](for-developers/site-publishing-and-domain-registering.md)
+  * [API Reference](for-developers/api-reference.md)
diff --git a/docs/for-developers/api-reference.md b/docs/for-developers/api-reference.md
index 2d299c3e..a662c569 100644
--- a/docs/for-developers/api-reference.md
+++ b/docs/for-developers/api-reference.md
@@ -1,11 +1,11 @@
 # API Reference
 
-How to work around with WebX's API, hosted at https://api.buss.lol.
+How to work around with WebX's API, hosted at <https://api.buss.lol>.
 
-This is the URI of the WebX API, which holds all the DNS of the network. You got different endpoints to do your stuff. https://api.buss.lol/.
+This is the URI of the WebX API, which holds all the DNS of the network. You got different endpoints to do your stuff. <https://api.buss.lol/>.
 
 {% hint style="warning" %}
-APIs have rate limits. They are provided in the headers.
+APIs have rate limits. They are provided in the headers and on the `GET /`'s response (plain text).
 {% endhint %}
 
 ## `GET` /
@@ -13,44 +13,58 @@ APIs have rate limits. They are provided in the headers.
 _Provides a basic message explaining the API._
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL            |
 | -------------- | --------------------- |
-| `GET`          | https://api.buss.lol/ |
+| `GET`          | <https://api.buss.lol/> |
 
 {% hint style="success" %}
+
 #### RETURNS
 
 ```txt
-Hello, world! The available endpoints are:
-GET /domains,
-GET /domain/:name/:tld,
-POST /domain,
-PUT /domain/:key,
-DELETE /domain/:key,
-GET /tlds.
-Ratelimits provided in headers.
+webxDNS v0.3.0!
+
+The available endpoints are:
+
+ - [GET] /domains
+ - [GET] /domain/{name}/{tld}
+ - [POST] /domain
+ - [PUT] /domain/{key}
+ - [DELETE] /domain/{key}
+ - [GET] /tlds
+
+Ratelimits are as follows: 5 requests per 10 minutes on `[POST] /domain`.
+
+Code link: https://github.com/face-hh/webx/tree/master/dns
 ```
+
 {% endhint %}
 
-## `GET` /domains`?amount={x}&page={y}`
+## `GET` /domains`?page_size={x}&page={y}`
 
-Being `amount` and `page` optional. `amount` for the amount of domains you want the response to have per page (defaults to 15), and `page` what page you want to view. _Allows you to get the list of all working domains from the network._
+Being `page_size` and `page` optional. `page_size` for the amount of domains you want the response to have per page (defaults to 15, max of 100), and `page` what page you want to view. _Allows you to get the list of all working domains from the network._
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
-| REQUEST METHOD | TARGET URL                   |
-| -------------- | ---------------------------- |
-| `GET`          | https://api.buss.lol/domains |
+| REQUEST METHOD | TARGET URL                     |
+| -------------- | ------------------------------ |
+| `GET`          | <https://api.buss.lol/domains> |
 
 {% hint style="success" %}
+
 #### RETURNS
 
 {% code title="response.json" overflow="wrap" lineNumbers="true" %}
+
 ```json
 {
     "domains": [
@@ -70,6 +84,7 @@ Being `amount` and `page` optional. `amount` for the amount of domains you want
     "limit": 15
 }
 ```
+
 {% endcode %}
 {% endhint %}
 
@@ -78,14 +93,17 @@ Being `amount` and `page` optional. `amount` for the amount of domains you want
 _Allows you to get the list of all valid TLDS._
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                |
 | -------------- | ------------------------- |
-| `GET`          | https://api.buss.lol/tlds |
+| `GET`          | <https://api.buss.lol/tlds> |
 
 {% hint style="success" %}
+
 #### RETURNS
 
 `200 OK`
@@ -93,6 +111,7 @@ _Allows you to get the list of all valid TLDS._
 ```json
 ["mf", "btw", "fr", "yap", "dev", "scam", "zip", "root", "web", "rizz", "habibi", "sigma", "now", "it", "soy", "lol", "uwu"]
 ```
+
 {% endhint %}
 
 ## `GET` /domain/`name`/`tld`
@@ -101,14 +120,17 @@ _Allows you to get the data from a specific domain._\
 _**Being**** ****`name`**** ****the domain name (e.g. "register") and**** ****`tld`**** ****it's TLD (e.g. "it").**_
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                           |
 | -------------- | ------------------------------------ |
-| `GET`          | https://api.buss.lol/domain/name/tld |
+| `GET`          | <https://api.buss.lol/domain/name/tld> |
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF DOMAIN DOES EXIST
@@ -120,9 +142,11 @@ _**Being**** ****`name`**** ****the domain name (e.g. "register") and**** ****`t
     "ip":"https://github.com/face-hh/webx-registrar"
 }
 ```
+
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF DOMAIN DOES NOT EXIST
 
 _Does not return anything._
@@ -133,12 +157,14 @@ _Does not return anything._
 _Allows you to register a domain from the API_
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                  | HEADERS                          |
 | -------------- | --------------------------- | -------------------------------- |
-| `POST`         | https://api.buss.lol/domain | `Content-Type: application/json` |
+| `POST`         | <https://api.buss.lol/domain> | `Content-Type: application/json` |
 
 {% hint style="info" %}
 _**AND BODY:**_
@@ -155,6 +181,7 @@ _Being `{name}` the `name` you want to use as the domain, `{tld}` the TLD you wa
 {% endhint %}
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF THE DOMAIN IS CREATED
@@ -169,9 +196,11 @@ _Being `{name}` the `name` you want to use as the domain, `{tld}` the TLD you wa
     "secret_key": "generated_secret_key"
 }
 ```
+
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF THE BODY OF YOUR `POST` REQUEST IS NOT VALID
 
 `400 Bad Request`
@@ -190,12 +219,14 @@ _Being `{name}` the `name` you want to use as the domain, `{tld}` the TLD you wa
 _Allows you to "search" for domains using domain names and TLDs_
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                        | HEADERS |
 | -------------- | --------------------------------- | ------- |
-| `POST`         | https://api.buss.lol/domain/check | _None_  |
+| `POST`         | <https://api.buss.lol/domain/check> | _None_  |
 
 {% hint style="info" %}
 _**AND BODY:**_
@@ -215,6 +246,7 @@ Quick reminder: unless specified, all parameters are required.
 {% endhint %}
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF THE DOMAIN IS CREATED
@@ -229,9 +261,11 @@ Quick reminder: unless specified, all parameters are required.
     "secret_key": "generated_secret_key"
 }
 ```
+
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF THE BODY OF YOUR `POST` REQUEST IS NOT VALID
 
 `400 Bad Request`
@@ -250,12 +284,14 @@ Quick reminder: unless specified, all parameters are required.
 _Allows you to update your domain's IP / GitHub URL. The code's source, basically._
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                       | HEADERS                          |
 | -------------- | -------------------------------- | -------------------------------- |
-| `PUT`          | https://api.buss.lol/domain/:key | `Content-Type: application/json` |
+| `PUT`          | <https://api.buss.lol/domain/:key> | `Content-Type: application/json` |
 
 {% hint style="info" %}
 _Being `:key` your domain's secret key._
@@ -272,6 +308,7 @@ _Being `{ip}` the new IP you want to set for your domain._
 {% endhint %}
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF THE IP IS CORRECTLY UPDATED
@@ -279,15 +316,18 @@ _Being `{ip}` the new IP you want to set for your domain._
 `200 OK`
 
 {% code title="response.json" overflow="wrap" lineNumbers="true" %}
+
 ```json
 {
     "ip": "new_ip"
 }
 ```
+
 {% endcode %}
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF THE BODY OF YOUR `PUT` REQUEST IS NOT VALID _OR_ SPECIFIED `KEY` IS NOT VALID
 
 `400 Bad Request`
@@ -302,18 +342,21 @@ _Being `{ip}` the new IP you want to set for your domain._
 _Allows you to delete your domain from the network. You cannot undo that, so be careful._
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                       | HEADERS               |
 | -------------- | -------------------------------- | --------------------- |
-| `DELETE`       | https://api.buss.lol/domain/:key | _No headers required_ |
+| `DELETE`       | <https://api.buss.lol/domain/:key> | _No headers required_ |
 
 {% hint style="info" %}
 _Being `:key` your domain's secret key._
 {% endhint %}
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF THE DOMAIN IS CORRECTLY REMOVED
@@ -322,6 +365,7 @@ _Being `:key` your domain's secret key._
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF THE REQUEST HAS AN INVALID PARAMETER
 
 `400 Bad Request`
@@ -340,12 +384,14 @@ This is disabled by default as you will need to come up with your own way of val
 {% endhint %}
 
 {% hint style="info" %}
+
 #### YOU SEND
+
 {% endhint %}
 
 | REQUEST METHOD | TARGET URL                            | HEADERS                                                      |
 | -------------- | ------------------------------------- | ------------------------------------------------------------ |
-| `POST`         | https://api.buss.lol/registry/domain/ | `Content-Type: application/json; Authorization = name:token` |
+| `POST`         | <https://api.buss.lol/registry/domain/> | `Content-Type: application/json; Authorization = name:token` |
 
 {% hint style="info" %}
 _Being `:token` your API key._
@@ -364,6 +410,7 @@ _Being `{name}` the `name` you want to use as the domain, `{tld}` the TLD you wa
 {% endhint %}
 
 {% hint style="success" %}
+
 #### RETURNS
 
 #### IF THE DOMAIN IS SUCCESSFULLY CREATED
@@ -378,9 +425,11 @@ _Being `{name}` the `name` you want to use as the domain, `{tld}` the TLD you wa
     "secret_key": "generated_secret_key"
 }
 ```
+
 {% endhint %}
 
 {% hint style="danger" %}
+
 #### IF THE BODY OF YOUR `POST` REQUEST IS NOT VALID
 
 `400 Bad Request`
diff --git a/docs/for-developers/css-3.25.md b/docs/for-developers/css-3.25.md
index 0de6e2d2..eafcc0b4 100644
--- a/docs/for-developers/css-3.25.md
+++ b/docs/for-developers/css-3.25.md
@@ -7,6 +7,7 @@ CSS 3.25 looks similar to regular CSS 3, but with some differences. Note that B9
 This is an example of a CSS 3.25 file.
 
 {% code title="styles.css" overflow="wrap" lineNumbers="true" %}
+
 ```css
 div {
     border-color: #616161;
@@ -78,16 +79,17 @@ hr {
     border-style: solid;
 }
 ```
+
 {% endcode %}
 
 Looks like a lot? It's not that complicated. It's just about taking a few things into account and then just checking a list of properties.
 
 ## Take into account
 
-1. **No selectors are required:** You don't need to use a dot to select a class (e.g. `.myClass {}`). Since there's no ID's to differentiate with, just put the class name without anything (e.g. `myClass{}`).
-2. **Use specific units:** Only **px** (which is translated to **pt**) for measures and **HEX** (#123456) for colors are supported. No RGBa, no HSL, no em, no viewport units...
+1. **No selectors are required:** You don't need to use a dot to select a class (e.g. `.myClass {}`). Since there's no ID's, you can just use the class name without anything (e.g. `myClass{}`).
+2. **Use specific units:** Only **px** (which sometimes is translated to **pt**) for measures and **HEX** (#123456) for colors is supported. No RGBa, no HSL, no em, no viewport units...
 3. **Remember how the CSS box model works:** We use CSS 3's standard box model, where a box has a SIZE, then a PADDING, then a BORDER and a MARGIN.
-4. **Events are not supported:** As of B9 v1.2.2, events (like `:focused`, `:hover`, and so on) are not supported.
+4. **Events are not supported:** As of B9 v1.3.1, events (like `:focused`, `:hover`, and so on) are not supported.
 
 Noted that? Now let's get to the styling features.
 
@@ -101,7 +103,7 @@ Noted that? Now let's get to the styling features.
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `padding`            | Any `px` value                                                                                                                                   | Gives the text a custom padding. Padding is the space inside of the box.                                                                                                                                                                                                              |
 | `margin-{direction}` | Any `px` value                                                                                                                                   | Gives the text a custom margin. Margin is the space outside of the box. **See "About margin" before using it"**                                                                                                                                                                       |
-| `border-width`       | Any `px` value                                                                                                                                   | Sets the width of the border. It acts as a summoning directive - this means that it needs to be declared and given a value greater than 0 for the border to be rendered in the first place. If you use any other `border-*` directive without declaring width, you won't see anything |
+| `border-width`       | Any `px` value                                                                                                                                   | Sets the width of the border. It acts as a "summoning directive". This means it needs to be declared and given a value greater than 0 for the border to be rendered. If you use any other `border-*` directive without declaring `border-width`, you won't see anything |
 | `border-color`       | Any `HEX` value                                                                                                                                  | Sets the color of the border.                                                                                                                                                                                                                                                         |
 | `border-style`       | Any of the following: `none`, `hidden`, `dotted`, `dashed`, `solid`, `double`, `groove`, `ridge`, `inset`, `outset`. _**Visual example below.**_ | Gives the border a custom style. _Since there are a lot of options, scroll down for an image preview of each one_.                                                                                                                                                                    |
 | `border-radius`      | Any `px` value                                                                                                                                   | Gives the border a custom roundness.                                                                                                                                                                                                                                                  |
@@ -109,9 +111,10 @@ Noted that? Now let's get to the styling features.
 | `background-color`   | Any `HEX` value                                                                                                                                  | Gives the item a background color. If not set, will use the default one depending on the user's theme (or not at all).                                                                                                                                                                |
 
 {% hint style="warning" %}
+
 #### About margin
 
-`margin` by itself is not supported by B9 as of 1.2.2. You need to give a direction. If you want to set the padding of the top of the box, use `margin-top`, for example.
+`margin` by itself is not supported by B9 as of 1.3.1. You need to give a direction. If you want to set the padding of the top of the box, use `margin-top`, for example.
 {% endhint %}
 
 | CSS 3.25 directive | Direction                |
@@ -121,8 +124,6 @@ Noted that? Now let's get to the styling features.
 | `margin-left`      | Left of the box          |
 | `margin-right`     | Right of the box         |
 
-
-
 {% hint style="info" %}
 <img src="../borderstyles.png" alt="Border preview" data-size="original">
 
@@ -138,7 +139,7 @@ Noted that? Now let's get to the styling features.
 | `gap`         | Any `px` value                                         | Sets the amount of space (in pixels) that will be created between all the elements that are inside of a `<div>`                                                                                                                                                 |
 | `direction`   | `row` or `column`                                      | The direction all the items inside of the `<div>` will follow. Default is `column`. Similar to CSS 3's flex display (_but no "display: flex;" required here_).                                                                                                  |
 | `wrap`        | `wrap` or `nowrap`                                     | If enabled, when there are too many elements inside of a parent container, they will be moved to the next line (they will be _wrapped_). If not, the elements will just overflow. Defaults to `nowrap`.                                                         |
-| `align_items` | Any of the following: `fill`, `start`, `end`, `center` | Defines if the items should be aligned to the center of the container, to the start, or to the end. If set to fill, the item will expand to fill all available horizontal space within its container instead of just moving to get aligned. Defaults to `fill`. |
+| `align-items` | Any of the following: `fill`, `start`, `end`, `center` | Defines if the items should be aligned to the center of the container, to the start, or to the end. If set to fill, the item will expand to fill all available horizontal space within its container instead of just moving to get aligned. Defaults to `fill`. |
 
 ### Text
 
@@ -148,7 +149,7 @@ Noted that? Now let's get to the styling features.
 | ------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `font-size`   | Any `px` value                                                                      | Gives the text a custom size. There is a default for each text tag (`h1`, `h2`, `p`...)                                                                                        |
 | `line-height` | Any `px` value                                                                      | Gives the text a custom line-height. There is a default for each text tag.                                                                                                     |
-| `font-family` | String value                                                                        | Gives the text a custom font. `<link>` does not support font files, so the end user must have that font installed. As of B9 v1.2.2, fallback fonts don't seem to be supported. |
+| `font-family` | String value                                                                        | Gives the text a custom font. `<link>` does not support font files, so the end user must have that font installed. As of B9 v1.3.1, fallback fonts don't seem to be supported. |
 | `font-weight` | Any of the following: `ultralight`, `light`, `normal`, `bold`, `ultrabold`, `heavy` | Gives the text a custom font weight.                                                                                                                                           |
 | `color`       | Any `HEX` value                                                                     | Gives the text a custom color.                                                                                                                                                 |
 
@@ -164,14 +165,14 @@ Noted that? Now let's get to the styling features.
 | --------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `strikethrough`       | `true` or `false`                                                | Gives the text a strikethrough.                                                                                                                      |
 | `strikethrough-color` | Any `HEX` value                                                  | If strikethrough is present, this will set the color of the strikethrough.                                                                           |
-| `overline`            | `none` or `single`                                               | Gives the text an overline (like an underline, but instead of under, over). Single is equivalent to "true" (but don't pass `true` as it won't work). |
-| `overline-color`      | Any `HEX` value                                                  | If overline is present, this will set the color of the overline.                                                                                     |
+| `overline`            | `none` or `single`                                               | Gives the text an overline (like an underline, but instead of under, over). Single is equivalent to "true" (but don't literally pass `true`; it won't work). |
+| `overline-color`      | Any `HEX` value                                                  | If overline is present, this sets the color of the overline.                                                                                     |
 | `underline`           | Any of the following: `none`, `single`, `double`, `low`, `error` | Gives the text an underline.                                                                                                                         |
 | `underline-color`     | Any `HEX` value                                                  | If underline is present, this will set the color of the overline.                                                                                    |
 
 ### Input and textarea
 
-> Width and height are considered "Layout" directives, but since they are only supported by `<input>` and `<textarea>` (as of B9 1.2.2), they have their own category for now.
+> Width and height are considered "Layout" directives, but they are only supported by `<input>` and `<textarea>` (as of B9 1.3.1), they have their own category for now.
 
 | Property | Possible value | Explanation                                   |
 | -------- | -------------- | --------------------------------------------- |
@@ -183,34 +184,32 @@ Noted that? Now let's get to the styling features.
 | Property              |
 | --------------------- |
 | `direction`           |
-| `align_items`         |
+| `align-items`         |
 | `width`               |
 | `height`              |
-| `line_height`         |
+| `line-height`         |
 | `color`               |
 | `wrap`                |
-| `background_color`    |
-| `font_family`         |
-| `font_weight`         |
+| `background-color`    |
+| `font-family`         |
+| `font-weight`         |
 | `underline`           |
-| `underline_color`     |
+| `underline-color`     |
 | `overline`            |
-| `overline_color`      |
+| `overline-color`      |
 | `strikethrough`       |
-| `strikethrough_color` |
-| `margin_top`          |
-| `margin_bottom`       |
-| `margin_left`         |
-| `margin_right`        |
-| `border_style`        |
-| `border_color`        |
-| `border_width`        |
-| `border_radius`       |
+| `strikethrough-color` |
+| `margin-top`          |
+| `margin-bottom`       |
+| `margin-left`         |
+| `margin-right`        |
+| `border-style`        |
+| `border-color`        |
+| `border-width`        |
+| `border-radius`       |
 | `padding`             |
-| `font_size`           |
+| `font-size`           |
 | `gap`                 |
 | `opacity`             |
 
-
-
 That would be it for styling! Now it's time for the fun part: scripting!
diff --git a/docs/for-developers/getting-started.md b/docs/for-developers/getting-started.md
index 592834a1..86567219 100644
--- a/docs/for-developers/getting-started.md
+++ b/docs/for-developers/getting-started.md
@@ -1,14 +1,14 @@
 # Getting started
 
-## Welcome to Web X development!
+## Welcome to Web X development
 
 {% hint style="info" %}
-Note this is guide is up to date for **B9 ENGINE - v1.2.2** (Napture and B9's version number are synchronized). If the browser gets a new release, wait for someone to commit / PR an update to the docs ([or make a commit yourself, if you feel like helping](https://github.com/face-hh/webx/tree/master/docs/)).
+Note this guide is up to date for **B9 ENGINE - v1.3.1** (Napture and B9's version number are synchronized). If the browser gets a new release, wait for someone to commit / PR an update to the docs.
 {% endhint %}
 
 ### What we'll see
 
-Web X websites are developed with HTML, CSS, and [Luau](https://luau-lang.org). In this guide, you'll basically find:
+Web X websites are developed with HTML++, CSS 3.25, and [Luau](https://luau-lang.org) (being HTML++ and CSS 3.25 basically HTML and CSS with a few changes). In this guide, you'll find:
 
 * Full syntax explained.
 * How to register a domain and upload your website to Web X.
@@ -16,45 +16,60 @@ Web X websites are developed with HTML, CSS, and [Luau](https://luau-lang.org).
 
 ### File structure
 
-Let's start with the basics. In order to make a web, you'll need to make a project with the following file structure:
+Let's start with the basics. In order to make a website, you'll need to make a project with the following file structure:
 
-```
+{% code title="Your project's root" overflow="wrap" lineNumbers="false" %}
+
+```txt
 /
 - index.html
 - styles.css
 - script.lua
 ```
 
+{% endcode %}
+
 {% hint style="warning" %}
 The index file **must** be called "index.html".
 {% endhint %}
 
-{% hint style="warning" %}
-As of version 1.2.2, Web X does **not** support routing, so no multiple pages (`/index.html`, `/hello.html`) are supported.
-{% endhint %}
+Routing is supported, so if you want to have multiple pages (like `buss://example.fr/second-page`), you can do that by creating folders with the name you want to give to the page, and creating another `index.html` file inside of that folder.
+
+{% code title="Your project's root" overflow="wrap" lineNumbers="false" %}
+
+```txt
+/
+- index.html
+- styles.css
+- script.lua
+    /second-page
+    - index.html
+```
 
-### Don't get confused
+{% endcode %}
 
-And hey, now that we talk about versioning, you might want to know this:
+Another thing you might want to take into account as we update B9 / Napture, is the meaning of each name.
 
 {% hint style="success" %}
+
 #### Don't get confused with naming
 
 Napture and B9 are connected, but they are not the same!
 
 * **Web X** - The entire project, including the DNS and all that stuff.
 * **Napture** - The browser itself, used to render websites using the B9 engine.
-* **B9 engine** (or just "B9") - Napture's rendering engine, which renders the HTML, CSS, and Luau. Most features will need to be supported by _this_, not by the browser itself. They both have the same version number. **Currently, the Latest version is v1.2.2**.
+* **B9 engine** (or just "B9") - Napture's rendering engine, which renders the HTML, CSS, and Luau. Most features will need to be supported by _this_, not by the browser itself. They both have the same version number. **Currently, the Latest version is v1.3.1**.
 
-_If an update releases and the documentation isn't up to date yet, you should see an alert at the beggining of this page. Contributors will try to keep this documentation up to date as soon as updates get released._
 {% endhint %}
 
 ### Dev menus and settings
 
-Plus, before starting, you might want to note these keybinds somewhere:
+Also, before starting, you might want to note these keybinds somewhere:
+
+| `CONTROL` + `SHIFT` + `S`          | `CONTROL` + `SHIFT` + `P`                                                                                                                 | `CONTROL` + `SHIFT` + `I`                                                 | `CONTROL` + `SHIFT` + `H`                                   |
+| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| This will open Napture's Settings. | This will open _Napture Logs_. This is made for developers, but it may help you understand why a page isn't working in case that happens. | This will open the built-in _GTK Inspector_. This is made for developers. | This will show the browser's history. |
 
-| `CONTROL` + `SHIFT` + `S`          | `CONTROL` + `SHIFT` + `P`                                                                  | `CONTROL` + `SHIFT` + `I`                                                                                             |
-| ---------------------------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
-| This will open Napture's Settings. | This will open _Napture Logs_. Here you'll see logs of what's going on with your own code. | This will open the _GTK Inspector_. Here you'll see logs of what's going on with GTK (the UI toolkit that powers B9). |
+And another thing: you probably develop from Visual Studio Code, as it's the most used code editor. For that, we recommend [KashTheKing](https://github.com/KashTheKing)'s [WebX Lua types extension](https://github.com/KashTheKing/webxluatypes), which will help you get better autocompletion and diagnostics when you write code for the WebX.
 
-Now, let's start! Go to the next pages to start learning how to write your own HTML, CSS, and Lua.
+Now, let's start! Go to the next pages to start learning how to write your own HTML++, CSS 3.25, and Lua.
diff --git a/docs/for-developers/html++.md b/docs/for-developers/html++.md
index 394b2b32..f8d90d95 100644
--- a/docs/for-developers/html++.md
+++ b/docs/for-developers/html++.md
@@ -2,11 +2,12 @@
 
 HTML++ looks similar to regular HTML5, but with some differences. Note that B9 is a new engine, not all classic HTML5 features are supported.
 
-## Basic structure.
+## Basic structure
 
 Same as regular HTML5, the `html` tag, with the `head` for metadata and `body` for your page's content.
 
 {% code title="index.html" overflow="wrap" lineNumbers="true" %}
+
 ```html
 <html>
   <head>
@@ -17,6 +18,7 @@ Same as regular HTML5, the `html` tag, with the `head` for metadata and `body` f
   </body>
 </html>
 ```
+
 {% endcode %}
 
 ## `<head>`: Metadata in HTML++
@@ -24,6 +26,7 @@ Same as regular HTML5, the `html` tag, with the `head` for metadata and `body` f
 A complete WebX head looks like this:
 
 {% code title="index.html" overflow="wrap" lineNumbers="true" %}
+
 ```html
 <head>
     <title>My cool web</title>
@@ -36,9 +39,10 @@ A complete WebX head looks like this:
     <script src="script.lua" />
 </head>
 ```
+
 {% endcode %}
 
-Let's explain everything. `<title>` and `<meta name="*">` are tags you know from classic HTML5. `<title>` will give a Title to your page, which will be displayed on both the browser's tab and the search results. `<meta name="description" content="*">` will give Dingle a description to show on the search results, and other meta tags may be used by websites that wish to embed Web X sites.
+Let's explain everything. `<title>` and `<meta name="*">` are tags you know from classic HTML5. `<title>` will give a Title to your page, which will be displayed on both the browser's tab and the search results, and `<meta name="description" content="*">` will give Dingle a description to show on the search results. Those are the HTML++ meta tags supported by Napture. **Note that other meta tags may be used by other websites that wish to embed Web X sites.**
 
 Now, let's go beyond the standard. You might wonder, why do links have no `rel` attribute? And why is the `script` tag self-closing? (which might even be rendered as an error by your IDE).
 
@@ -47,16 +51,15 @@ Now, let's go beyond the standard. You might wonder, why do links have no `rel`
 You can link images (as much as you like), stylesheets and scripts (only 1 of each type).
 
 {% hint style="info" %}
-Audio and video support are being worked on, but as of B9 1.2.2 they are not supported. [See PR](https://github.com/face-hh/webx/pull/150).
+Audio and video support are being worked on, but as of B9 1.3.1 they are not supported. [See PR](https://github.com/face-hh/webx/pull/150).
 {% endhint %}
 
 The thing is, B9 does not use `rel` to define what to do with each thing. It uses the **order** of your tags, being the first tag of each kind the one that will be used for it's specific purpose. In other words: your first `<link>` has to href an image and will be your site's icon, your second `<link>` has to href a stylesheet and will be the source for the page's CSS, and your `<script>` tag should be the third one, and will be the source for the page's Luau script.
 
-{% hint style="warning" %}
-This isn't the standard web, **HTTPS is supported only by the \<script> tag**. Both (CSS & Lua) files must be available locally, in the same path as the `index.html`. As we told you before, the three files must be in the root. HTTP(S) is supported for the icon's link and for images. We recommend using Imgur.
-{% endhint %}
+HTTPS is supported for `src` and `href` attributes, if you want to link external Luau scripts, images, or stylesheets. Later on you'll also see that you can import Luau scripts from the script itself. Also, images have support for `base64` in both the `src` property of the HTML++ tag and on the Luau `set_content()` function (which you'll learn to use later).
 
 {% code title="index.html" overflow="wrap" lineNumbers="true" %}
+
 ```html
 <head>
     <title>My cool web</title>
@@ -79,6 +82,7 @@ This isn't the standard web, **HTTPS is supported only by the \<script> tag**. B
   <script src="script2.lua" />
 </body>
 ```
+
 {% endcode %}
 
 {% hint style="info" %}
@@ -101,18 +105,19 @@ Currently, you can use the following HTML tags:
 * Divisions (`<div>`), basically containers where you can put your tags to organise your page.
 * Lists, which can be ordered (`<ol>`) or unordered (`<ul>`). Both can have list items (`<li>`) in them.
 * Horizontal rule (`<hr>`), which creates a horizontal line on the entire page.
-* Images (`<img>`), with a `src` property for the local path / HTTP URI of the image. They are unresizeable, so your image must already be of the desired size (use any image editing tool for that, e.g. [GIMP](https://www.gimp.org/)).
+* Images (`<img>`), with a `src` property for the local path / HTTP URI of the image. They are unresizeable, so your image must already be the desired size (use any image editing tool for that, e.g. [GIMP](https://www.gimp.org/)).
 
 {% hint style="warning" %}
-Additionally, **as of B9 v1.2.2** images are currently broken on _Windows_; and will only work if you follow the [Guide of Compilation for Napture - Windows.](https://github.com/face-hh/webx?tab=readme-ov-file#windows-1)
+Additionally, **as of B9 v1.3.1** images are currently broken on _MS Windows_ and will only work if you follow the [Guide of Compilation for Napture - Windows.](https://github.com/face-hh/webx?tab=readme-ov-file#windows-1)
 {% endhint %}
 
 * Inputs (`<input>`) are one-line text fields. You can interact with them with Web X's Lua API.
 * Textareas (`<textarea>`) are equivalent to inputs, but they are _multi-line_ text fields instead of _one-line_.
-* Dropdowns (`<select>`), which can have options in them (`<option>`).
+* Buttons (`<button>`), which can be clicked by the user to do something. You can detect clicks with Web X's Lua API.
+* Dropdowns (`<select>`), which can have options inside of them (`<option>`).
 
 {% hint style="warning" %}
-As of B9 1.2.2, dropdowns are purely decorative at the moment as they don't have a Lua API.
+As of B9 1.3.1, dropdowns are purely decorative at the moment as they don't have a Lua API.
 {% endhint %}
 
 We're done with the HTML++, **but you must note one more thing**.
diff --git a/docs/for-developers/luau.md b/docs/for-developers/luau.md
index 6d384c87..64471874 100644
--- a/docs/for-developers/luau.md
+++ b/docs/for-developers/luau.md
@@ -3,15 +3,16 @@
 Luau is a typed scripting language derived from Lua. Instead of JavaScript, we use Luau to power Web X.
 
 {% hint style="info" %}
-Note: We say "Luau" as it is what we use in our backend, but you do not need to install it. **You can write regular Lua and your code will work fine.**
+Note: Sometimes we say "Luau" as it is what we use in our backend, but you do not need to install it. **You can write regular Lua and your code will work fine.**
 {% endhint %}
 
-## SET and GET.
+## SET and GET
 
 The Luau API is as simple as learning two things: you can SET and you can GET. You can GET to access elements from your page's HTML++, and you can SET to modify them.
 
 {% hint style="info" %}
-#### You come from JavaScript?
+
+### You come from JavaScript?
 
 GET would be equivalent to your `document.*` query selectors and getElementById / getElementbyClassName, while SET would be equivalent to give a value to props like "href", "opacity", and so on.
 {% endhint %}
@@ -21,37 +22,43 @@ GET would be equivalent to your `document.*` query selectors and getElementById
 In fact, the function to get an element is just called "get".
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 local my_item = get("my_item")
 ```
+
 {% endcode %}
 
 > Much shorter compared to JS :wink:
 
 {% code title="javascript.js" overflow="wrap" lineNumbers="true" %}
+
 ```js
 // too long
 document.querySelector("h1")
 // even longer!?
 document.getElementByClassName("my_item")
 ```
+
 {% endcode %}
 
 Note that we use the same function to get items by their tag name or by their class.
 
 **Remember the end of the HTML++ page, where we told you to avoid setting a class name with the same name as a tag?** It's because of this, `get("a")` will get an anchor, so you should not give an item a class name of `class="a"`.
 
-> What about "`querySelectorAll()`?
+> What about "`querySelectorAll()`"?
 
 **Just add "true" to the `get` function to get all the elements of the same class / tag name.**
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 -- Will give a single anchor
 local all_hyperlinks = get("a");
 -- Will give all anchors (or hyperlinks, them the way you prefer)
 local all_hyperlinks = get("a", true);
 ```
+
 {% endcode %}
 
 {% hint style="success" %}
@@ -63,6 +70,7 @@ When you don't pass `true`, if you select a tag or a class name that is repeated
 Now, to interact with the element, you can use `get_{prop}` **and `set_{prop}`** functions. Here's an example:
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 local myanchor = get("a")
 
@@ -73,15 +81,17 @@ print(myurl)
 -- This will SET the href property to a new value
 myanchor.set_href("buss://dingle.it")
 ```
+
 {% endcode %}
 
 It's that easy! _Scroll to the bottom for a list of available SET and GET directives._
 
-### Events
+## Events
 
 The Luau API has also support for detecting **events**. Similar to JS's `onclick`. To use them, create a function that's called on an event, just like you would do in JS. Example:
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 get("button").on_click(function()
     print("The button got clicked!!!")
@@ -91,9 +101,10 @@ get("input").on_input(function(content)
     print(content)
 end)
 ```
+
 {% endcode %}
 
-{% hint style="success" %}
+{% hint style="info" %}
 `on_input` is only supported by `<input>` and `<textarea>`
 {% endhint %}
 
@@ -101,11 +112,12 @@ end)
 Output from the `print()` function will be logged by Napture Logs. As we told you before, you can open them with `CONTROL` + `SHIFT` + `P`
 {% endhint %}
 
-### HTTP Fetching
+## HTTP Fetching
 
 If you need to make an HTTP request to interact with an API, you can use the `fetch` function. It should look like this:
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 local test = true;
 
@@ -116,23 +128,64 @@ local res = fetch({
     body = '{ "test": ' .. test .. '}'
 })
 ```
+
 {% endcode %}
 
 Variable names are self explanatory, you give the function the `URL` you want to fetch, the HTTP method you want to use, which can be "GET", "POST", "DELETE", etc..., the headers of the HTTP request, and the body, which would be the content itself of your request.
 
-### Full lists
+## Other things you might want to note
+
+{% hint style="info" %}
+Remember, unlike the JS you're used to on the standard webs, arrays don't start at 0: **they start at 1**.
+
+{% code title="javascript.js" overflow="wrap" lineNumbers="true" %}
+
+```js
+// World Wide Web JS
+const firstp = document.getElemenyById("first-parragraph");
+const secondp = document.getElemenyById("second-parragraph");
+const thirdp = document.getElemenyById("third-parragraph");
+let fruits = ['apple', 'banana', 'cherry'];
+
+firstp.textContent = fruits[0]; // 'apple'
+secondp.textContent = fruits[1]; // 'banana'
+thirdp.textContent = fruits[2]; // 'cherry'
+```
+
+{% endcode %}
+
+{% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
+```lua
+-- Bussin WebX Lua
+local firstp = get("first-parragraph")
+local secondp = get("second-parragraph")
+local thirdp = get("third-parragraph")
+local fruits = {'apple', 'banana', 'cherry'}
+
+firstp.set_content(fruits[0]) -- 'ERROR'
+
+firstp.set_content(fruits[1]) -- 'apple'
+thirdp.set_content(fruits[2]) -- 'banana'
+thirdp.set_content(fruits[3]) -- 'cherry'
+```
+
+{% endcode %}
+{% endhint %}
+
+## Full lists
 
 All the `get_{x}`, `set_{x}` and `on_{x}` available functions.
 
 {% hint style="success" %}
-On every function, whenever `x` is expected to be a string or a number, it can always be passed both as a string/number directly or as a Lua variable.
+In every function, whenever `x` is expected to be a string or a number, you can always pass it directly as a string/number or as a Lua variable.
 {% endhint %}
 
-#### GET
+### MAIN GET FUNCTION
 
 <table data-header-hidden><thead><tr><th></th><th></th><th width="144"></th><th></th><th></th></tr></thead><tbody><tr><td>Function</td><td>x</td><td>y</td><td>Return</td><td>Explanation</td></tr><tr><td><code>get(x, y)</code></td><td><code>x</code> must be the tag name or class name of the target item. It should be a string.</td><td>Can be <code>true</code> or can just not be passed at all.</td><td>A "Tag" class (or more, if <code>true</code>), functions below.</td><td>Allows to get HTML tags to interact with. Gets an element using it's tag name or class name. If you pass true as the second argument, every instance with the same class / every instance of the tag will be selected at once. If not, the first match will be chosen.</td></tr></tbody></table>
 
-#### GETTING FUNCTIONS
+#### OTHER GET FUNCTIONS
 
 | Function         | Return                                                                                                                                                                  | Explanation                           |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
@@ -144,6 +197,7 @@ On every function, whenever `x` is expected to be a string or a number, it can a
 Example usage of GET and GETTING FUNCTIONS
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 -- GET
 local test = get("myclass")
@@ -156,36 +210,50 @@ local content = get("h1").get_contents()
 -- GET every p tag
 local all_paragraphs = get("p", true)
 ```
+
 {% endcode %}
 
-#### SET
+### SET FUNCTIONS
 
 | Function          | x                                                                                                                 | Explanation                                                                                                                                                                                                        |
 | ----------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `set_contents(x)` | `x` should be a string.                                                                                           | Gets the text content of any item.                                                                                                                                                                                 |
+| `set_content(x)` | `x` should be a string.                                                                                           | Sets the text content of any item.                                                                                                                                                                                 |
 | `set_href(x)`     | `x` must be the URL you want to set the `href` property to. It should be a string.                                | Sets the `href` value of an anchor.                                                                                                                                                                                |
 | `set_source(x)`   | `x` must be the URL or base64 that you want to set the `src` property to. It should be a string.                  | Sets the `src` value of an image.                                                                                                                                                                                  |
 | `set_opacity(x)`  | `x` must be the value you want to set the `opacity` property to. It should be a float between 0 and 1.            | Sets the `opacity` value of any item.                                                                                                                                                                              |
-| `set_visible(x)`  | `x` must be the value you want to set the `visible` property to. It should be a boolean value, `true` or `false`. | :warning: **Upcoming feature** - _**Not released yet (as of B9 1.2.2)**_ - Changes if the item is visible or not. It's just visual, elements never get removed from the code and are always accessible from there. |
+| `set_visible(x)`  | `x` must be the value you want to set the `visible` property to. It should be a boolean value, `true` or `false`. | Changes if the item is visible or not. It's just visual, elements never get removed from the code and are always accessible from there. |
+| `set_timeout(function(), x)`  | `x` must be the desired amount of time to wait, in miliseconds. | Allows to set a timeout, which basically means the code will wait for the specified amount of time before executing. |
 
 Example usage of SET
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 -- first, we get
 local test = get("myclass")
 
 -- now, we set
 test.set_opacity(0.75)
-test.set_contents("This text will be set as the content of the element")
+test.set_content("This text will be set as the content of the element")
 
 -- example: get an anchor and set it's href to the Dingle search engine and its text content to "Search with Dingle"
 get("a").set_href("buss://dingle.it")
-get("a").set_contents("Search with Dingle")
+get("a").set_content("Search with Dingle")
+
+-- example: get a button and get a heading, and when it gets clicked, wait 5 seconds and then set the h1's text to "you waited :D"
+local h1 = get("myheading")
+local btn = get("mybutton")
+
+btn.on_click(function()
+    set_timeout(function()
+        h1.set_content("You waited :D")
+    end, 5000)
+)
 ```
+
 {% endcode %}
 
-#### EVENTS
+### EVENTS
 
 > Event functions do not have a return. As showed before, put them inside of a function. Every time they get triggered the code of the functions will be executed.
 
@@ -198,12 +266,13 @@ get("a").set_contents("Search with Dingle")
 Example usage of EVENTS
 
 {% code title="script.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 local test = get("mybutton")
 
 -- now, we do stuff when it gets clicked
 test.on_click(function()
-    test.set_contents("i was clicked!")
+    test.set_content("i was clicked!")
 end)
 
 -- a slightly more complex example:
@@ -212,24 +281,29 @@ local input = get("input") -- will get an <input> item
 local h1 = get("h1")
 
 input.on_submit(function()
-    h1.set_contents("your input was: " + input.get_contents())
+    h1.set_content("your input was: " + input.get_contents())
 )
 ```
+
 {% endcode %}
 
-#### OTHER FUNCTIONS
+### OTHER FUNCTIONS
 
 | Function   | x                                                           | Return                                                | Explanation                                 |
 | ---------- | ----------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
 | `print(x)` | `x` can be any type.                                        | No return.                                            | Will print `x` to Napture Logs.             |
 | `fetch(x)` | `x` must be an array with the contents of the HTTP request. | Returns the response of the HTTP request as a string. | Allows to make HTTP requests to fetch APIs. |
+| `require(x)` | `x` must be an URL that links to a `.lua` file. | Returns the content of the required Lua file | Allows to load external Lua code. It will be loaded, executed, and do whatever you need it to do as if it was on your own script. |
+| `time()` | _No parameters passed_ | Returns the current time. | Allows to get the current time. Uses seconds instead of milliseconds like Lua's standard `os.time()` function. |
 
 {% hint style="info" %}
+
 #### About fetch
 
 This is what `x` (the content of your request) should look like:
 
 {% code title="fetch.lua" overflow="wrap" lineNumbers="true" %}
+
 ```lua
 local response = fetch({
     url = "https://api.buss.lol/",
@@ -238,9 +312,40 @@ local response = fetch({
     body = '{ "test": ' .. test .. '}' -- REQUEST BODY
 })
 ```
+
 {% endcode %}
 
 Basically `url`, `method`, `headers`, and `body`. Remember that `fetch` will return whatever the HTTP request itself returns (the HTTP response, basically).
 {% endhint %}
 
+### GLOBAL OBJECTS
+
+- `json` - Includes `json.stringify(x)` (being `x` a Lua array) and `json.parse(x)` (being `x` a string). As the names tell, json. `stringify` turns a Lua array into a JSON string, and `parse` does the opposite.
+
+### GLOBAL VARIABLES
+
+You are also provided with a bunch of variables you can access to work around with your website, being these:
+
+- `window.query` - If the window has a query, returns it. For example, `window.query` in a website that has this query: `buss://hello.fr?q=wiki`, would return the following:
+
+{% code title="Return (Lua)" overflow="wrap" lineNumbers="true" %}
+
+```lua
+{
+  ["q"] = "wiki"
+}
+```
+
+{% endcode %}
+
+- `window.location` - Returns the current URL. For example, printing `window.location` when the user is in `buss://hello.fr/hi` would return the following:
+
+{% code title="Return (Lua)" overflow="wrap" lineNumbers="true" %}
+
+```lua
+"hello.fr/hi"
+```
+
+{% endcode %}
+
 And that's it! You're ready to write fully functional WebX code! However, we're not done yet. Your beautiful code must be published to the WebX somehow, right? Let's find out about that.
diff --git a/docs/for-developers/site-publishing-and-domain-registering.md b/docs/for-developers/site-publishing-and-domain-registering.md
index 3fd4b2d1..ca3cd344 100644
--- a/docs/for-developers/site-publishing-and-domain-registering.md
+++ b/docs/for-developers/site-publishing-and-domain-registering.md
@@ -16,47 +16,80 @@ You have basically two options:
 
 ### Self hosting
 
-Set-up your own server _**the way you like**_, and get a static IP address for it. Make sure it's serving your `index.html` in the root of the IP, and that the other files (CSS 3.5, Luau) are also in the root. Images don't need to be in the root, they can also be retrieved from HTTP routes. Note the IP, as later we'll use it to serve our website.
+Set up your own server _**the way you like**_, and get a static IP address for it. Make sure it's serving your `index.html` in the root of the IP, and that the other files (e.g. the CSS 3.5 file, Luau file, images...) are also in the root. Images don't need to be in the root, they can also be retrieved from HTTP routes. Note the IP, as later we'll use it to serve our website.
 
 ### GitHub
 
 GitHub makes it way easier for the Web X network to function. Create your own repository with whatever name you'd like it to have and upload your files. Copy the full HTTPS URL of the repo (`https://github.com/{username}/{repo}`) and keep it, as we'll use it later. That would be it!
 
-Now that you have your IP / GitHub URL, you just need to register a domain, provide the URL / IP to Bussin's API systems, and your website should be up and running.
+Now that you have your IP / GitHub URL, you just need to register a domain, provide the URL / IP to WebX's API systems, and your website should be up and running.
 
 ## Getting my domain
 
 Domains can be registered via our API (see [next page](api-reference.md#post-domain)). There are different providers, like these ones:
 
-{% hint style="danger" %}
-#### Outdated section
-
-This section contains content from contributors and 3rd parties. It has been marked as outdated. This alert will stay until the content below gets updated.
-{% endhint %}
-
-<table><thead><tr><th>Provider</th><th width="243">Where to find it</th><th width="149">Administrator</th><th width="156">Recommended</th><th>Notes</th></tr></thead><tbody><tr><td>Bussin Registrar</td><td>Go to <code>buss://register.it</code> on your Web X browser.</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2714">✔️</span> <strong>Official Web X service</strong></td><td>YES</td><td>Open source</td></tr><tr><td>WebX Registry</td><td>Go to <a href="https://kitty.yachts/"><code>https://kitty.yachts/</code></a> on a WWW browser.</td><td>tlochsta</td><td>???</td><td><em>No notes.</em></td></tr></tbody></table>
+<table>
+    <thead>
+        <tr>
+            <th>
+                Provider
+            </th>
+            <th width="243">
+                Where to find it
+            </th>
+            <th width="149">
+                Administrator</th>
+            <th width="156">
+                Recommended
+            </th>
+            <th>
+                Notes
+            </th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>Bussin Registrar</td>
+            <td>Go to <code>buss://register.it</code> on your Web X browser.</td>
+            <td><span data-gb-custom-inline data-tag="emoji" data-code="2714">✔️</span> <strong>Official Web X service</strong></td>
+            <td>YES</td>
+            <td>Open source</td>
+        </tr>
+        <tr>
+            <td>WebX Registry</td>
+            <td>Go to <a href="https://kitty.yachts/"><code>https://kitty.yachts/</code></a> on a WWW browser.</td>
+            <td>[tlochsta](https://discord.com/users/795039947656134728)</td>
+            <td>???</td>
+            <td><em>No notes.</em></td>
+        </tr>
+    </tbody>
+</table>
+
+> **Note:** This does **not** include registrars for other DNS systems.
 
 Of course, we recommend using the official Bussin Registrar, which looks kinda like this:
 
 ![Screenshot](../png4.png)
 
-What we care about is the Publish form. Every other registrer should use the same format, asking for an IP, TLD, and website name.
+What we care about is the "Publish" form. Every other registrar should use the same format, asking for an IP, TLD, and website name.
 
 ### Domain parameters
 
 Your domain needs three simple things.
 
 {% hint style="info" %}
+
 #### Website name
 
 The name of your website for the URL. It will be here:
 
 buss://**{here}**.tld
 
-Note that there is a max of 24 characters for your domain, and it can't contain offensive terms.
+Note that there is a max of 24 characters for your domain, and it can't contain offensive terms. See [rules](#community-rules) for more info.
 {% endhint %}
 
 {% hint style="info" %}
+
 #### TLD
 
 The Top-Level Domain you'd like your website to have. It will be here:
@@ -92,14 +125,15 @@ In a nutshell, choose from "mf", "btw", "fr", "yap", "dev", "scam", "zip", "root
 {% endhint %}
 
 {% hint style="info" %}
+
 #### IP
 
-The IP / GitHub URL I told you about before. Give it to the system so it can access it and serve your website.
+The IP / GitHub URL we told you about before. Provide it to the system so it can access the files hosted in there and serve your website to the WebX.
 {% endhint %}
 
 ### Community Rules
 
-Web X is supervised by the team at Bussin, who administrates the Web X API. Any website that doesn't follow these rules will be removed.
+Web X is supervised by the Bussin team, who's members administrate the Web X API. Any website that doesn't follow these rules will be terminated.
 
 1. If your website contains Not Safe For Work material of any kind, it will be removed.
 2. If your website contains frequent racial slurs, references made in bad faith to tragic events, racism towards other races, or anything of that kind, it will be removed.
@@ -114,41 +148,45 @@ Web X is supervised by the team at Bussin, who administrates the Web X API. Any
 11. If your website's domain contains words or content that are considered against any of the rules listed before, it will be removed.
 
 {% hint style="danger" %}
+
 ### BUSSIN WEB X COMMUNITY RULES AGREEMENT
 
 By publishing content to this platform ("Bussin Napture"/"Bussin WebX"), _**you agree to comply with all rules and regulations set forth by the administrators**_. **The administrators reserve the right to interpret and enforce these rules at their discretion.**
 {% endhint %}
 
 {% hint style="warning" %}
+
 #### Reporting websites that don't follow the rules
 
 To report websites that are not following the listed rules, please use [the Discord server](https://discord.gg/cNwWvdWj42) or contact `FaceDev` on [Twitter](https://twitter.com/facedevstuff) or Discord.
 {% endhint %}
 
-If you submit a website that is not against the rules, you should start seeing it on the Dingle search  results (after \~12 hours at max) and in your `buss://` URL. Plus, your domain provider should give you a "Secret key".
+If you submit a website that is not against the rules, you should start seeing it on the Dingle search  results (after \~12 hours at max) and in your `buss://` URL. Plus, the domain provider you used for registering the domain should also give you a "Secret key".
 
 {% hint style="danger" %}
 VERY IMPORTANT THING ABOUT YOUR SECRET KEY
 
-#### DO NOT LOSE IT AND DO NOT SHARE IT WITH ANYONE.
+#### DO NOT LOSE IT AND DO NOT SHARE IT WITH ANYONE
+
+**Do not lose it** because it is required if you want to edit the IP / GitHub URL you want your website to be server from, or if you want to shut down your domain.
 
-Do not lose it because it is required if you want to edit your IP or shut down your domain, and do not share it with anyone because it can compromise your website.
+**Do not share it** with anyone because if anyone gets access to it, your website can get compromised.
 {% endhint %}
 
 {% hint style="info" %}
 It doesn't work!
 
-#### 1. Code not matching the Web X standard.
+#### 1. Code not matching the Web X standard
 
 If your site doesn't work, check if your code is correct. Maybe it's that.
 
-#### 2. The rate limit.
+#### 2. The rate limit
 
 There is a global cooldown on how many domains can be registered. Current rate is of _**100 domains per hour**_, globally.
 
-#### 3. The API being down.
+#### 3. The API being down
 
-Web X is a recently setup project and it's uptime is not of a 100%. It could be down for repairing.
+Web X is a recently setup project and it's uptime is not 100%. It could be down for repairing.
 
 For these reasons we recommend joining [the Discord server](https://discord.gg/cNwWvdWj42), where the development team keeps everyone updated on issues with the network.
 {% endhint %}
diff --git a/docs/for-users/advanced-user-manual.md b/docs/for-users/advanced-user-manual.md
index b161a7a4..1ef10001 100644
--- a/docs/for-users/advanced-user-manual.md
+++ b/docs/for-users/advanced-user-manual.md
@@ -4,24 +4,22 @@ This short page includes some additional things you might want to know about how
 
 ## Keybinds
 
-| `CONTROL` + `SHIFT` + `S`          | `CONTROL` + `SHIFT` + `P`                                                                                                                 | `CONTROL` + `SHIFT` + `I`                                                 |
-| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
-| This will open Napture's Settings. | This will open _Napture Logs_. This is made for developers, but it may help you understand why a page isn't working in case that happens. | This will open the built-in _GTK Inspector_. This is made for developers. |
+| `CONTROL` + `SHIFT` + `S`          | `CONTROL` + `SHIFT` + `P`                                                                                                                 | `CONTROL` + `SHIFT` + `I`                                                 | `CONTROL` + `SHIFT` + `H`                                   |
+| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| This will open Napture's Settings. | This will open _Napture Logs_. This is made for developers, but it may help you understand why a page isn't working in case that happens. | This will open the built-in _GTK Inspector_. This is made for developers. | This will show the browser's history. |
 
 ## Using other browsers
 
-{% hint style="danger" %}
-#### Outdated section
-
-This section contains content from contributors and 3rd parties. It has been marked as outdated. This alert will stay until the content below gets updated.
-{% endhint %}
-
 Since Web X is an open-source network, there are different browsers available, like the following:
 
-| Provider       | Where to get it it                                                                                          | Maintainer                                            | Recommended                                                                                                                              |
-| -------------- | ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| Bussin Napture | Go to the [releases tab of the official Web X repository](https://github.com/face-hh/webx/releases/latest). | :heavy\_check\_mark: **Official Web X service**       | YES                                                                                                                                      |
-| Bussinga       | Go to the [Bussinga repository](https://github.com/codingMASTER398/bussinga/releases/latest).               | [codingMASTER398](https://github.com/codingMASTER398) | YES if you are a Windows user. As of Napture 1.2.2, Bussinga 0.0.1 seems to work better on MS Windows. **Webview based**.                |
-| Fapture        | Go to the [Fapture repository](https://github.com/nojasm/fapture/)                                          | [nojasm](https://github.com/nojasm/)                  | Kind off. Compatible with both CSS 3.25 and standard CSS 3. Has no releases and needs to be compiled by the end user. **Webview based**. |
+| Browser | Where to get it it | Maintainer | Compatible |
+| ------- | ------------------ | ---------- | ---------- |
+| Bussin Napture | Go to the [releases tab of the official Web X repository](https://github.com/face-hh/webx/releases/latest). | :heavy\_check\_mark: **Official Web X service** | Windows+, Linux+++ |
+| Bussinga | Go to the [Bussinga repository](https://github.com/webx-plus/bussinga/releases/latest). | [WebX Plus organisation](https://github.com/WebX-Plus) | Windows++, Linux+++ |
+| Fapture | Go to the [Fapture repository](https://github.com/nojasm/fapture/) | [nojasm](https://github.com/nojasm/) | NodeJS & Compiled by user, in theory +++ on all platforms |
 
 **Something is wrong with this table? As 3rd party browsers get updated, this table can get outdated over time.** [**Make a PR to help keep it up to date.**](https://github.com/face-hh/webx/tree/master/docs) **Thanks in advance!**
+
+## Using other DNS
+
+Napture and other browsers also give you the ability to choose a different DNS. In Napture, you can change this by clicking the `CTRL` + `SHIFT` + `S` keybind to open settings and change the DNS to the URL of the DNS server you'd like to use. A good example of a different WebX DNS is the [WebX Plus DNS](https://dns-one.webxplus.org/).
diff --git a/docs/for-users/basic-user-manual.md b/docs/for-users/basic-user-manual.md
index 7376a8c7..84de2bfd 100644
--- a/docs/for-users/basic-user-manual.md
+++ b/docs/for-users/basic-user-manual.md
@@ -1,8 +1,8 @@
 # User manual
 
-## First thing first: Install Napture.
+## First thing first: Install Napture
 
-<figure><img src="../.gitbook/assets/image.png" alt=""><figcaption><p>Bussin Napture v1.2.2</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image.png" alt=""><figcaption><p>Bussin Napture v1.3.1</p></figcaption></figure>
 
 This is the guide to install **Bussin Napture**, the official Web X browser.
 
@@ -10,23 +10,27 @@ This is the guide to install **Bussin Napture**, the official Web X browser.
 
 * Download [Rust](https://www.rust-lang.org/tools/install). Then, you just need to open `install-linux.sh` as an executable (if you can't execute it, first do `sudo chmod +x ./install-linux.sh`, then you should be able to install).
 
+> `install-linux.sh` is available in the `/napture` folder of the WebX repository. You'll need to download the entire folder from [here](https://github.com/face-hh/webx/tree/master/napture).
+
 ### macOS
 
 * Download [Rust](https://www.rust-lang.org/tools/install) and [Homebrew](https://brew.sh). Then, you just need to open `install-macos.sh` as an executable (if you can't execute it, first do `chmod +x ./install-macos.sh`, then you should be able to install).
 
+> `install-macos.sh` is available in the `/napture` folder of the WebX repository. You'll need to download the entire folder from [here](https://github.com/face-hh/webx/tree/master/napture).
+
 ### Windows
 
 * Install the executable from the [release tab](https://github.com/face-hh/webx/releases). It's a self-extractor with WinRAR because it has a lot of DLLs.
 
 ### Arch Linux
 
-Run **`yay -S napture`**. It's available on AUR.
+Run **`yay -S napture`**. Napture is available on AUR.
 
 ### Nix\[OS]
 
 **Flakes**: The repository provides a flake which exposes an overlay providing the webx package, so you could just add the input in your flake.nix file
 
-```nix{3}
+```nix
 {
     inputs = {
         webx.url = "github:face-hh/webx";
@@ -36,7 +40,7 @@ Run **`yay -S napture`**. It's available on AUR.
 
 Then add it to your overlays and install it
 
-```nix{3}
+```nix
 { inputs, ... }: {
     nixpkgs.overlays = [
         inputs.webx.overlays.x86_64-linux.default
@@ -48,7 +52,7 @@ Then add it to your overlays and install it
 
 Add it to either home.packages (home manager) or environment.systemPackages (global packages).
 
-```nix{2}
+```nix
 home.packages = with pkgs; [
     webx
 ];
diff --git a/napture/README.md b/napture/README.md
index a09e1a4e..89956bf9 100644
--- a/napture/README.md
+++ b/napture/README.md
@@ -1,10 +1,13 @@
 # Bussin Napture
+
 This folder contains the source code for **Bussin Napture**, the official Bussin Web X **browser**.
 
 The file structure:
-- `src/b9` - B9 is the codename for Napture's rendering engine. It is responsible for handling HTML, CSS and Lua.
+
+- `src/b9` - B9 is the codename for Napture's rendering engine. It is responsible for handling, parsing, and rendering HTML++, CSS 3.25 and Lua.
 
 Other info:
+
 - To support more tags, take a look at [GTK Widget Galery](https://docs.gtk.org/gtk4/visual_index.html). You'd have to modify the `render_body` function in `src/b9/html.rs`.
 - To support more CSS properties, take a look at `src/b9/css.rs`. Each element has different methods & properties, so you'll have to add a default value.
-- To add more Lua functions, take a look at `src/b9/lua.rs`.
\ No newline at end of file
+- To add more Lua functions, take a look at `src/b9/lua.rs`.