Merge pull request #200 from HOSTED-POWER/BjarneVO-KBrestructure

Bjarne vo k brestructure

Author: BjarneVO

TurboStack Platform/Hosts/Accounts/accountclone.md

@@ -5,7 +5,7 @@ icon: upload
 
 #  Cloning an account
 
-To make a clone of an existing application, we provide the **Clone Account** feature. This function replicates the entire configuration and copies the files and database, enabling a quick and efficient setup with minimal effort.
+To make a clone of an **existing application**, we provide the **Clone Account** feature. This function **replicates the entire configuration** and **copies the files and database**, enabling a quick and efficient setup with minimal effort.
 
 !!!Info
 This feature is extremely useful to quickly copy your production environment to a staging environment or vice versa!
@@ -26,6 +26,4 @@ Here’s how to do it:
 6. The server will now clone the account, indicated by the **publishing** indicator in the top left.
 ![](../../../img/turbostackapp/newapp/publishing.png)
 7. If the account clone has succeeded, it will be indicated in the top right with a timestamp.
-![](../../../img/turbostackapp/newapp/publishsuccess.png)
-
-And that’s it! Your application is now cloned to a new account. Be sure to save the configuration and publish it when you're ready.
+![](../../../img/turbostackapp/newapp/publishsuccess.png)

TurboStack Platform/Hosts/Accounts/credentials.md

@@ -11,7 +11,7 @@ Make sure you have already created an existing user with a successful publish.
 !!!
 
 You can fetch the credentials from the application you just created.
-To do this, click on the gear icon next to the user and navigate to the **Database Info** tab.
+To do this, click on the **gear icon** next to the user and navigate to the **Database Info** tab.
 
 ![](../../../img/turbostackapp/newapp/tsa_gearwheel.png)
 To get database credentials:

TurboStack Platform/Hosts/Accounts/databaseusers.md

@@ -6,7 +6,7 @@ label: Extra database users
 
 ## Adding extra database users
 
-It is possible to add an additional database user with read-only or admin access to a databases. You can also retrieve the credentials for this user.
+It is possible to add an **additional database user** with **read-only** or **admin** access to a databases. You can also retrieve the **credentials** for this user.
 ![](../../../img/turbostackapp/newapp/tsa_extra_db_user1.png)
 ![](../../../img/turbostackapp/newapp/tsa_extra_db_user2.png)
 **admin**: Full access to ALL server databases.  

TurboStack Platform/Hosts/Accounts/migrationhero.md

@@ -12,15 +12,15 @@ To simplify the migration of your external application to TurboStack, the **Migr
 If you want to migrate an application from TurboStack to TurboStack, please use the **Account Cloning** feature documented below.
 !!!
 
-Before starting, make sure you have already created an application and successfully performed a **Save and Publish**.
+Before starting, make sure you have already **created an application** and successfully performed a **Save and Publish**.
 
 1. Navigate to the **Accounts** tab in the TurboStack Platform under your host.
 ![](../../../img/turbostackapp/newapp/tsa_user6.png)
 
 2. Click **Migration Hero**.
 ![](../../../img/turbostackapp/newapp/tsa_migration_hero1.png)
 
-3. In the next step, enter the remote host and the user you want to migrate. 
+3. In the next step, enter the **remote host** and the **user** you want to migrate. 
 Then, choose the authentication method you want to use to connect to the remote host.
 ![](../../../img/turbostackapp/newapp/tsa_migration_hero2.png)
 
@@ -30,10 +30,10 @@ Then, choose the authentication method you want to use to connect to the remote
 5. **Option 2:** Generate and add the provided public SSH key to the `.ssh/authorized_keys` file on the remote host, then click **Next**.
 ![](../../../img/turbostackapp/newapp/tsa_migration_hero4.png)
 
-6. Choose the destination account (it must be an existing one) and select whether to migrate the database, files, or both. Then click **Next**. 
+6. Choose the **destination account** (it must be an existing one) and select whether to **migrate the database, files, or both**. Then click **Next**. 
 ![](../../../img/turbostackapp/newapp/tsa_migration_hero5.png)
 
-7. Select the hostname(s) you want to associate with the account and choose the type of certificate to activate. Click **Start Import** to begin the migration.
+7. Select the **hostname(s)** you want to associate with the account and choose the **type of certificate** to generate. Click **Start Import** to begin the migration.
 ![](../../../img/turbostackapp/newapp/tsa_migration_hero6.png)
 
 8. A migration progress popup will appear in the bottom-right corner. Once it finishes, your migration is complete. 

TurboStack Platform/Hosts/Accounts/setup.md

@@ -4,15 +4,15 @@ icon: plus-circle
 ---
 # Setup
 
-This article explains how to set up your application environment from scratch. If you want to replicate an existing environment, or want to migrate an application from an external server to TurboStack, please consult the [Account Cloning](accountclone.md) and [Migration Hero](migrationhero.md) articles respectively.
+This article explains how to set up your application environment from scratch. If you want to **replicate an existing environment**, or want to **migrate an application from an external server to TurboStack**, please consult the [Account Cloning](accountclone.md) and [Migration Hero](migrationhero.md) articles respectively.
 
 !!! info
-New servers can also be auto-configured using **Templates**! Visit [this](../../templates.md) page for more information.
+New servers can also be autoconfigured using **Templates**! Visit [this](../../templates.md) page for more information.
 !!!
 
 ## What is an account and what is it used for?
 
-The account is a linux user which can be used simply to access the server. However, you probably want to deploy one or multiple **applications** under this user. This guide will explain how to deploy system users and all settings your application requires.
+The account is a **Linux user** which can be used simply to access the server. However, you probably want to deploy one or multiple **applications** under this user. This guide will explain how to deploy system users and all settings your application requires.
 
 !!!
 For staging and production instances of an application, best practice is always to use an entirely different server, because it's by design unavoidable that resources allocated for staging, will be (silently) "taken away" from production. Even when this staging application is rarely used, it would still consume memory for e.g. databases, causing avoidable overhead.
@@ -37,7 +37,7 @@ Creating a new user on the [TurboStack Platform](https://my.turbostack.app "Turb
 ![](../../../img/turbostackapp/newapp/tsa_user4.png)
 ### Deploying a new account in the source YAML [!badge icon="alert" text="Advanced"]
 
-Advanced users can also deploy an account in the source YAML:
+Advanced users can also deploy an account in the **source YAML**
 
 ```yaml
 system_users:
@@ -46,7 +46,7 @@ system_users:
 
 ![](../../../img/turbostackapp/newapp/tsa_user5.png)
 
-More info on using the YAML editor can be found [here](../yaml.md).
+More info on using the **YAML editor** can be found [here](../yaml.md).
 
 ## Creating a new application
 
@@ -113,6 +113,6 @@ system_users:
 
 ![](../../../img/turbostackapp/newapp/tsa_app11.png)
 
-More info on using the YAML editor can be found [here](../yaml.md).
+More info on using the **YAML editor** can be found [here](../yaml.md).
 
 

TurboStack Platform/Hosts/advancedtab.md

@@ -15,20 +15,20 @@ The **advanced** tab offers some more advanced configuration options for specifi
 
 **DKIM (DomainKeys Identified Mail)** is an email authentication method that helps prevent email spoofing. It works by adding a **digital signature** to outgoing messages, which receiving mail servers can verify using the **public key** published in the sender’s domain DNS records. This sections allows you to easily set up DKIM for your mail domain.
 
-1. Fill in the FQDN (Fully Qualified Domain Name), which is the domain you want to mail from.
-2. Choose a selector for the DKIM record. This selector will be used as the subdomain part of the record.
-3. SSH to the server and use the command `tscli dkim records` to acquire your DKIM record.
-4. Create the DKIM record in your domain's DNS settings
-5. SSH to the server and use the command `tscli dkim validate` to check if the DNS record was created correctly.
+1. Fill in the **FQDN (Fully Qualified Domain Name)**, which is the domain you want to mail from.
+2. Choose a **selector** for the DKIM record. This selector will be used as the **subdomain** part of the record.
+3. SSH to the server and use the command `tscli dkim records` to **acquire your DKIM record**.
+4. **Create the DKIM record** in your domain's DNS settings
+5. SSH to the server and use the command `tscli dkim validate` to check if the **DNS record was created correctly**.
 6. All done!
 
 !!! info
-DKIM is part of your domain's mail deliverability optimisation. For more information on mail deliverability, take a look [here](../../Configuration/Mail/deliverability.md).
+DKIM is part of your domain's mail **deliverability** optimisation. For more information on mail deliverability, take a look [here](../../Configuration/Mail/deliverability.md).
 !!!
 
 ### Mail Devtool - Enabling mail capturing and mail testing
 
-TurboStack allows you to use either Mailpit or Mailhog to test your mailing. Once activated, you can reach the GUI through the URLs https://<hostname>/mailpit or https://<hostname>/mailhog respectively. Here, a basic auth prompt will appear, where you can enter the [system user's credentials](Accounts/credentials.md).
+TurboStack allows you to use either **Mailpit** or **Mailhog** to test your mailing. Once activated, you can reach the GUI through the URLs https://<hostname>/mailpit or https://<hostname>/mailhog respectively. Here, a basic auth prompt will appear, where you can enter the [system user's credentials](Accounts/credentials.md).
 
 !!! info
 We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer receiving updates.
@@ -40,23 +40,23 @@ We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer
 
 ### Varnish Cache Size
 
-This value determines the amount of memory that can be used by Varnish to store cached content. The default setting auto-scales based on your server flavour, but can be set to a size of your preference.
+This value determines the **amount of memory** that can be used by Varnish to store cached content. The default setting **auto-scales** based on your server flavour, but can be set to a size of your preference.
 
 ### Use your own Varnish custom VCL
 
-Your Varnish is set up to use a default VCL (Varnish Configuration Language) based on and optimised for your selected app_type. However, you can use your own VCL if you wish. To do so, toggle this option on and add your VCL file to the directory /etc/varnish/conf.d/ on your server.
+Your Varnish is set up to use a **default VCL** (Varnish Configuration Language) based on and optimised for your selected **app type**. However, you can use your own VCL if you wish. To do so, toggle this option on and add your VCL file to the directory `/etc/varnish/conf.d/` on your server.
 
 ### Varnish Flavor
 
-Choose between the Open Source and Enterprise versions of Varnish. The Open Source flavor is free, while the Enterprise version requires you to buy a seperate license. 
+Choose between the **Open Source** and **Enterprise** versions of Varnish. The Open Source flavor is free, while the Enterprise version requires you to buy a **separate license**. 
 
-The Open Source flavor includes an option to enable Varnish modules.
+The Open Source flavor includes an option to **enable Varnish modules**.
 
 ## RabbitMQ Options
 
 ![RabbitMQ Options](img/advancedtabrabbitmq.png)
 
-The RabbitMQ Plugins options allows you to easily install RabbitMQ plugins.
+The RabbitMQ Plugins options allows you to easily **install RabbitMQ plugins**.
 
 ## FTP  Server Options
 
@@ -68,26 +68,26 @@ Generate an SSL certificate for FTP connections using a hostname of your choice.
 
 ### Enable SFTP for FTP Users
 
-Enables SFTP connections over port 222 using the existing FTP daemon and users. This does not work over port 22, as this is reserved for the SSH service.
+Enables SFTP connections over **port 222** using the existing FTP daemon and users. This does not work over port 22, as this is reserved for the SSH service.
 
 ## Operating System
 
 ![Operating System](img/advancedtaboperatingsystem.png)
 
 ### OS Extra Packages
 
-A non-exhaustive list of packages to be installed. Please note this list is not complete, and more options are available when using source YAML mode! More info on editing YAML can be found [here](yaml.md)
+A non-exhaustive list of packages to install. Please note this list is not complete, and more options are available when using source YAML mode! More info on editing YAML can be found [here](yaml.md)
 
 ### Maintenance Window
 
-Set a maintenance window for patches and updates that require rebooting the server. This allows you to choose your least critical timing for this essential maintenance.
+Set a maintenance window for **patches and updates** that require rebooting the server. This allows you to choose your **least critical timing** for essential updates.
 
 ## Advanced Database Monitoring
 
 ![img.png](img/advancedtabdatabasemonitoring.png)
 
-Allows you to set up the database monitoring tool PMM (Percona Monitoring and Management) on your TurboStack. 
+Allows you to set up the database monitoring tool **PMM (Percona Monitoring and Management)** on your TurboStack. 
 
-If you have a pmm advanced database analytics system, you can fill in the PMM master server's hostname to link your TurboStack server to it. The PMM Sampling Rate can be set in Advanced Settings.
+If you have a PMM advanced database analytics system, you can fill in the **PMM master server's hostname** to link your TurboStack server to it. The **PMM Sampling Rate** can be set in Advanced Settings.
 
 More information on PMM can be found [here](https://docs.percona.com/percona-monitoring-and-management/3/index.html).

TurboStack Platform/Hosts/general.md

@@ -13,7 +13,7 @@ Before we get down to the details, let's look into some general functionality:
 
 #### 1. Switch between the GUI layout and the (advanced) YAML layout
 
-You can deploy your server using the GUI, or if you're more of an infrastructure-as-code nerd, you can dive straight into the YAML. Any changes you make in either GUI or YAML will be reflected in the other, so feel free to try both!
+You can deploy your server using the **GUI**, or if you're more of an **infrastructure-as-code** nerd, you can dive straight into the **YAML**. Any changes you make in either GUI or YAML will be reflected in the other, so feel free to try both!
 
 For more information on configuring your server using YAML, click [here](yaml.md).
 
@@ -23,18 +23,18 @@ If you want to set YAML as default, you can do so by clicking the icon on the to
 
 #### 2. Revisions: shows all historic configuration changes made to the server
 
-We all make mistakes, but we have you covered: The revision function allows you to review the full history of server configuration changes and revert to a past version at the click of a button.
+We all make mistakes, but we have you covered: The **revision function** allows you to review the **full history** of server configuration changes and **revert to a past version** at the click of a button.
 
 #### 3. Fetch the credentials and IPs of the server's users and databases
 
-The credentials button gives you a full overview of all your server credentials, including system users, database users, FTP users, etc.
+The **Credentials** button gives you a full overview of all your server credentials, including system users, database users, FTP users, etc.
 
 #### 4. Save any changes made to the configuration
 
 Save your changes when settings have been modified, without deploying the changes to the server.
 
 #### 5. Save and Publish: saves and deploys the changes made to the server
 
-Save the changes you've made to the configuration, and immediately deploy them to the server. There is also an option to save & full publish, which will ensure everything is deployed, as opposed to only the changes.
+Save the changes you've made to the configuration, and immediately **deploy** them to the server. There is also an option to **save & full publish**, which will ensure **everything** is deployed, as opposed to only the changes.
 
 The following pages describe configuration options for all tabs in the host management console.

TurboStack Platform/Hosts/groupstab.md

@@ -5,8 +5,8 @@ icon: people
 
 # Groups tab
 
-Groups make it possible to apply certain settings across multiple TurboStack nodes, such as time zones or SSH key access. 
+Groups make it possible to **apply certain settings across multiple TurboStack nodes**, such as time zones or SSH key access. 
 
 ![Groups Tab](img/groupstab.png)
 
-This section of the Hosts management allows you to apply or remove Groups you have created separately to and from the current server. More info on what Groups are and how to manage them can be found [here](../groups.md).
+This section of the **Hosts** management allows you to apply or remove Groups you have created separately to and from the current server. More info on what Groups are and how to manage them can be found [here](../groups.md).

TurboStack Platform/Hosts/monitoring.md

@@ -4,7 +4,7 @@ icon: eye
 ---
 # Monitoring
 
-Hosted Power proactively monitors your infrastructure to ensure server and service availability while simultaneously tracking resource usage. It alerts you if the load is too high, disk space is running low, or other critical thresholds are met, helping you maintain optimal performance.
+Hosted Power proactively **monitors your infrastructure** to ensure server and service **availability** while simultaneously tracking **resource usage**. It alerts you if the load is too high, disk space is running low, or other critical thresholds are met, helping you maintain optimal performance.
 
 The general health of the server can be seen in the TurboStack Platform overview:
 
@@ -15,12 +15,12 @@ The general health of the server can be seen in the TurboStack Platform overview
 3. CPU load and usage
 4. Disk usage
 
-If any of these checks alert, the icons will become red. When this is the case, please contact the Hosted Power support asap.
+If any of these checks alert, the icons will become red. When this is the case, please contact the [Hosted Power Support](../../Support/standard_support.md) asap.
 
 ## Website monitoring URL
 
-The TurboStack Platform is also able to monitor a website URL per application. In this case, the website URL will be added to our monitoring system
-and Hosted Power will monitor the availability of the website based on the URL, and intervene 24/7 if an issue arises.
+The [TurboStack Platform](https://my.turbostack.app/ "TurboStack Platform") is also able to **monitor a website URL** per application. In this case, the website URL will be added to our monitoring system
+and Hosted Power will **monitor the availability** of the website based on the URL, and **intervene 24/7** if an issue arises.
 
 Please follow the instructions below to activate the monitoring url on your server