doc: Use name The Things Stack Enterprise (#850)

doc/content/getting-started/aws/ami/deployment-guide/_index.md

@@ -61,7 +61,7 @@ This template allows the user to customize the deployment. The following is a li
 |---|---|---|
 |EC2 Instance Name|Name of the EC2 instance.|`the-things-enterprise-stack`|
 |Domain|Domain name. You should be able to configure DNS for the domain. TLS certificates from Let's Encrypt will automatically be requested.|-|
-|Network Title*|The title of your deployment.|`The Things Enterprise Stack for LoRaWAN`|
+|Network Title*|The title of your deployment.|`The Things Stack Enterprise for LoRaWAN`|
 |CIDR block|CIDR block used by the VPC.|10.0.0.0/16|
 
 > \* Optional field

doc/content/getting-started/aws/ami/post-deployment/_index.md

@@ -5,7 +5,7 @@ weight: 2
 aliases: "/guides/aws/ami/after-deploy"
 ---
 
-This section provides the information necessary to get started with The Things Enterprise Stack after it is deployed via [AWS Marketplace](https://aws.amazon.com/marketplace/pp/The-Things-Industries-The-Things-Enterprise-Stack/B081HZKDJ4) using AWS CloudFormation.
+This section provides the information necessary to get started with {{% tts %}} after it is deployed via [AWS Marketplace](https://aws.amazon.com/marketplace/pp/The-Things-Industries-The-Things-Enterprise-Stack/B081HZKDJ4) using AWS CloudFormation.
 
 <!--more-->
 
@@ -40,21 +40,21 @@ Once the domain has been propagated, the DNS Lookup will show that your Domain (
 
 ### SSL Certificates
 
-As a security measure, plaintext access to the Console/API is disabled. In order to serve requests securely, The Things Enterprise Stack has built-in support to automatically request, serve and renew SSL certificates.
+As a security measure, plaintext access to the Console/API is disabled. In order to serve requests securely, {{% tts %}} has built-in support to automatically request, serve and renew SSL certificates.
 
 Apart from the DNS mapping above, no additional steps are necessary for this.
 
 ## Getting Started using the Console
 
-Please check the [Console]({{< ref "/getting-started/console" >}}) guide to get quickly started with The Things Enterprise Stack Console.
+Please check the [Console]({{< ref "/getting-started/console" >}}) guide to get quickly started with {{% tts %}} Console.
 
 ## Getting Started using the Command Line Interface (CLI)
 
-Please check the [CLI]({{< ref "/getting-started/cli" >}}) guide to get quickly started with The Things Enterprise Stack CLI.
+Please check the [CLI]({{< ref "/getting-started/cli" >}}) guide to get quickly started with {{% tts %}} CLI.
 
 ## SSH Access
 
-In most cases, you will interact with The Things Enterprise Stack only via the Console or the CLI. However, in case there is a need to directly access the EC2 instance, there is an option to do so via SSH.
+In most cases, you will interact with {{% tts %}} only via the Console or the CLI. However, in case there is a need to directly access the EC2 instance, there is an option to do so via SSH.
 
 SSH access is possible only via the IP addresses set using the **Restrict SSH Access to IP Range** parameter during deployment. Also, the SSH client needs access to the private key corresponding to the public key that was chosen in the **SSH Key** parameter during deployment. The SSH username is `ec2-user`.
 
@@ -76,14 +76,14 @@ This directory is structured as follows:
 ├── acme                        # contains SSL certificates and related files
 ├── bootstrap                   # contains logs generated during deployment and restarts
 └── lorawan-stack
-    ├── config.yml              # The Things Enterprise Stack configuration
+    ├── config.yml              # The Things Stack Enterprise configuration
     ├── environment             # additional environment variables
     ├── lorawan-frequency-plans # contains a local copy of the LoRaWAN Frequency Plans Repository
     ├── public                  # contains the static assets
-    └── tti-lw-stack            # The Things Enterprise Stack binary
+    └── tti-lw-stack            # The Things Stack Enterprise binary
 ```
 
-The Things Enterprise Stack binary is run as a `systemd` service. In order to check the logs, run the following:
+{{% tts %}} binary is run as a `systemd` service. In order to check the logs, run the following:
 
 ```bash
 sudo journalctl -f -u lorawan-stack.service
@@ -103,6 +103,6 @@ Please check the [Adding Devices]({{< relref "devices/adding-devices" >}}) guide
 
 ## AWS IoT
 
-The Things Enterprise Stack supports publishing of uplink messages directly to the [AWS IoT suite](https://aws.amazon.com/iot/). In order for this to work, the **AWS IoT Telemetry** option in the CloudFormation template must be set to **true** during the deployment phase.
+{{% tts %}} supports publishing of uplink messages directly to the [AWS IoT suite](https://aws.amazon.com/iot/). In order for this to work, the **AWS IoT Telemetry** option in the CloudFormation template must be set to **true** during the deployment phase.
 
 Please check the guide on [AWS IoT]({{< relref "integrations/cloud-integrations/aws-iot" >}}) guide for more information.

doc/content/getting-started/aws/ami/updating/_index.md

@@ -15,7 +15,7 @@ We recommend using [Change Sets](https://docs.aws.amazon.com/AWSCloudFormation/l
 On the AWS Console, open the **CloudFormation** service, navigate to the **Change sets** tab and select **Create change set**. There are two choices that can be made here:
 
 - Use current template: Choose this option to update input parameters on an existing template.
-- Replace current template: Choose this option to use a new template on the existing deployment. This option should be used to apply new versions of The Things Enterprise Stack that are delivered as new version of the CloudFormation template.
+- Replace current template: Choose this option to use a new template on the existing deployment. This option should be used to apply new versions of {{% tts %}} that are delivered as new version of the CloudFormation template.
 
 Once the necessary options are updated, select the **Create Change Set** option. This will create a change set that describes the resources that will be updated by this change and if any of these resources need to be replaced. 
 

doc/content/getting-started/aws/ecs/monitoring/_index.md

@@ -17,8 +17,8 @@ The provided Prometheus image already comes with a number of recording and alert
 For all ECS services that form your {{% tts %}} deployment, the following alerts are defined:
 
 - `NoIdentityServers` (The cluster does not have any Identity Server instances). This means that there are no ECS tasks for the Identity Server component.
-- `SomeIdentityServersDown` (Some Identity Server instances of The Things Enterprise Stack are down). This means that some of the Identity Server instances are not responding. In many cases the deployment will still be online, as requests are routed to other instances.
-- `AllIdentityServersDown` (All Identity Server instances of The Things Enterprise Stack are down). This means that none of the Identity Server instances is responding.
+- `SomeIdentityServersDown` (Some Identity Server instances of {{% tts %}} are down). This means that some of the Identity Server instances are not responding. In many cases the deployment will still be online, as requests are routed to other instances.
+- `AllIdentityServersDown` (All Identity Server instances of {{% tts %}} are down). This means that none of the Identity Server instances is responding.
 
 Similar alerts are defined for the Gateway Server, Network Server, Application Server, Join Server, etc.
 
@@ -28,15 +28,15 @@ For the deployment as a whole, the following alerts are defined:
 - `UpcomingCertificateExpiry` (A TLS certificate expires in less than 14 days).
 - `CertificateExpired` (A TLS certificate has expired).
 - `IncreasedLatency` (An instance is experiencing increased latency).
-- `UpcomingLicenseExpiry` (The Things Enterprise Stack license expires in less than 14 days).
-- `LicenseExpired` (The Things Enterprise Stack license expired).
+- `UpcomingLicenseExpiry` ({{% tts %}} license expires in less than 14 days).
+- `LicenseExpired` ({{% tts %}} license expired).
 
 For several components there are alerts that fire when traffic patterns deviate from "usual" traffic:
 
-- `GatewayServerReceivedUplinkTrafficDrop` (The Gateway Server of The Things Enterprise Stack received less uplink traffic than usual). This alert includes the protocol (UDP, MQTT, WS), so make sure to look at that when this alert fires.
-- `GatewayServerForwardedUplinkTrafficDrop` (The Gateway Server of The Things Enterprise Stack forwarded less uplink traffic than usual). This alert includes the host (cluster, packet broker), so make sure to look at that when this alert fires. If the host is "cluster", there may be an issue with the Network Server. If the host is "packetbroker", there may be an issue with the Packet Broker Agent.
-- `NetworkServerReceivedUplinkTrafficDrop` (The Network Server of The Things Enterprise Stack received less uplink traffic than usual).
-- `ApplicationServerReceivedUplinkTrafficDrop` (The Application Server of The Things Enterprise Stack received less uplink traffic than usual).
+- `GatewayServerReceivedUplinkTrafficDrop` (The Gateway Server of {{% tts %}} received less uplink traffic than usual). This alert includes the protocol (UDP, MQTT, WS), so make sure to look at that when this alert fires.
+- `GatewayServerForwardedUplinkTrafficDrop` (The Gateway Server of {{% tts %}} forwarded less uplink traffic than usual). This alert includes the host (cluster, packet broker), so make sure to look at that when this alert fires. If the host is "cluster", there may be an issue with the Network Server. If the host is "packetbroker", there may be an issue with the Packet Broker Agent.
+- `NetworkServerReceivedUplinkTrafficDrop` (The Network Server of {{% tts %}} received less uplink traffic than usual).
+- `ApplicationServerReceivedUplinkTrafficDrop` (The Application Server of {{% tts %}} received less uplink traffic than usual).
 
 Similar alerts for downlink traffic will be added in the future.
 

doc/content/getting-started/cloud-hosted/_index.md

@@ -5,7 +5,7 @@ aliases: [/guides/cloud-hosted/cloud-hosted]
 weight: 6
 ---
 
-The Things Industries offers The Things Enterprise Stack as hosted software as a service (SaaS). 
+The Things Industries offers {{% tts %}} as hosted software as a service (SaaS). 
 
 This guide explains what that means and shows how to work with The Things Industries Cloud.