Merge pull request #3422 from travis-ci/DU-22/Heading-updates

Du 22/heading updates

Author: DominikAlberski

user/enterprise.md

@@ -24,7 +24,7 @@ integrates with GitHub.com, enabling you to have greater control over your secur
 to scale out your build infrastructure as needed.
 
 
-## Why choose Enterprise over travis-ci.com?
+## Why Enterprise over travis-ci.com
 
 Travis CI Enterprise is built to bring the features of the [hosted
 platform](/user/travis-pro) to different development processes. So whether you
@@ -88,18 +88,18 @@ Travis CI Enterprise requires a certain infrastructure for deployment. It curren
 
 ![Travis CI Enterprise About page](/images/TCIE-architecture1.png)
 
-### Travis CI Enterprise consists of two major parts:
+### Travis CI Enterprise Core Services and Worker
 
 1. TCI services (or TCI Core Services), responsible for integration with version control systems, authorizing builds, scheduling build jobs, etc.
 2. TCI Worker and build environment images (also called OS images).
 
-#### TCI Core services require the following:
+#### TCI Enterprise Core Services 
 
 1. A PostgreSQL11 (or later) database.
 2. An infrastructure to deploy a Kubernetes cluster; it can be deployed in a server cluster or in a single machine if required
 3. Depending on your setup, you may want to deploy and configure some of the components on your own, e.g., RabbitMQ - see the [Setting up Travis CI Enterprise](/user/enterprise/tcie-3.x-setting-up-travis-ci-enterprise/) for more details.
 
-#### TCI Worker requires the following:
+#### TCI Enterprise Worker
 
 1. An infrastructure where a docker image containing the Worker and a linked build image can be deployed.
 2. Connectivity to certain Travis CI Core Services components - see the [Setting Up Worker](/user/enterprise/setting-up-worker/) for more details.
@@ -130,7 +130,7 @@ Set up Travis CI Enterprise by heading over our [set up](/user/enterprise/tcie-3
 
 Or if you need more information on Travis CI, head back and view our [core concepts](/user/for-beginners/), the [Onboarding](/user/onboarding/) guide, or the [tutorials](/user/tutorials/tutorials-overview/).
 
-## Contact
+## Contact Enterprise Support
 
 {{ site.data.snippets.contact_enterprise_support }}
 

user/enterprise/Multi-CPU-Builds.md

@@ -4,7 +4,7 @@ layout: en_enterprise
 
 ---
 
-## Multi CPU builds
+## Enable Multi CPU builds
 
 If you wish to build on different multiple CPU architectures (ARM64, IBM PowerPC, IBM Z) and own or manage respective infrastructure, it is possible to do so using Travis CI.
 
@@ -18,3 +18,7 @@ In order to enable the capability of building on multiple CPU architectures, the
 The MultiCPU environment runs as LXD containers within an LXD host. Once the infrastructure is set up, developers can use it by simply modifying the .travis.yml in the repository.  Please see our [Multi CPU documentation](https://docs.travis-ci.com/user/multi-cpu-architectures/) for usage examples.
 
 Please see [deployment](https://docs.travis-ci.com/user/enterprise/setting-up-worker/) and [configuration](https://docs.travis-ci.com/user/enterprise/worker-configuration/) instructions on preparing Travis CI Enterprise to build against various CPU architectures.
+
+## Contact Enterprise Support
+
+{{ site.data.snippets.contact_enterprise_support }}

user/enterprise/bionic.md

@@ -14,13 +14,13 @@ We recommend using a **compute optimized** machine with 8 vCPUs and ~16 GB of me
 
 > A single worker machine can only be used together with one build environment. If you would like to setup additional build environments (such as Xenial or Focal), please provision an additional machine.
 
-## Third party apt repositories and services disabled by default
+## Third-party apt repositories and services disabled by default
 
 [Third party apt-repositories are removed](https://docs.travis-ci.com/user/reference/bionic/#third-party-apt-repositories-removed) to help reduce risk of unrelated interference and allow for faster apt-get updates.
 
 [Services disabled by default](https://docs.travis-ci.com/user/reference/bionic/#services-disabled-by-default) to speed up boot time and improve performance.
 
-## Installation with Travis CI Enterprise 2.2.6 and later
+## Install Bionic with Travis CI Enterprise 2.2.6 or higher
 
 To install the Bionic build environment on a new server, run the commands below:
 
@@ -33,7 +33,7 @@ $ sudo bash /tmp/installer.sh \
 --travis_build_images=bionic
 ```
 
-## Restarting `travis-worker`
+## Restart the travis-worker
 
 After installation, or when configuration changes are applied to the worker, restart the worker as follows:
 
@@ -43,7 +43,7 @@ $ sudo systemctl restart travis-worker
 
 Worker configuration changes are applied on start.
 
-## Running Builds in the Bionic Build Environment
+## Run Builds in the Bionic Build Environment
 
 To run a project's builds in the new Bionic build environment, please add a `dist: bionic` to your `.travis.yml` file.
 

user/enterprise/build-images.md

@@ -1,5 +1,5 @@
 ---
-title: Customizing Travis CI Enterprise Build Images
+title: Customize Travis CI Enterprise Build Images
 layout: en_enterprise
 
 ---
@@ -9,7 +9,7 @@ development process and improve the build environment and performance.
 
 
 
-## Customizing Build Images
+## Customize Build Images
 
 After pulling the build images from
 [quay.io](https://quay.io/organization/travisci) either through
@@ -61,7 +61,7 @@ you can run:
       docker -H tcp://0.0.0.0:4243 rm travis_ruby
 ```
 
-## Enabling Docker Builds
+## Enable Docker Builds
 
 ### Worker machine configuration
 

user/enterprise/custom-queues.md

@@ -49,7 +49,7 @@ production:
 
 See the [example](#advanced-configuration-yaml-example) for details on syntax. Click 'Save' on the Management Console Settings when you are ready. Travis CI Enterprise will restart with your new queue settings.
 
-### Advanced Configuration YAML Example
+### Advanced Configuration YAML
 
 The syntax for the **Advanced Configuration YAML** field is very important. Incorrect syntax will result in builds being routed to defaults, usually a `builds.linux` queue, depending on if there are any modifications to your installation. Here's an example of a custom queue definition:
 

user/enterprise/focal.md

@@ -1,9 +1,11 @@
 ---
-title: Focal Build Containers for Enterprise (beta)
+title: Focal Build Containers for Enterprise
 layout: en_enterprise
 
 ---
 
+> Note: Focal Build Containers for Enterprise is a beta feature. 
+
 ## System Setup
 
 **Platform Requirements**: To use the Focal build containers, the Travis CI Enterprise (TCIE) installation must be at version 3.0 or higher.
@@ -15,13 +17,13 @@ We recommend using a **compute optimized** machine with 8 vCPUs and ~16 GB of me
 
 > A single worker machine can only be used together with one build environment. If you would like to setup additional build environments (such as Xenial or Focal), please provision an additional machine.
 
-## Third party apt repositories and services disabled by default
+## Third-party apt repositories and services disabled by default
 
 [Third party apt-repositories are removed](https://docs.travis-ci.com/user/reference/focal/#third-party-apt-repositories-removed) to help reduce risk of unrelated interference and allow for faster apt-get updates.
 
 [Services disabled by default](https://docs.travis-ci.com/user/reference/focal/#services-disabled-by-default) to speed up boot time and improve performance.
 
-## Installation with Travis CI Enterprise 3.0 and later
+## Install Focal with Travis CI Enterprise 3.0 or higher
 
 On a new server, please run the commands below to install the Focal build environment:
 
@@ -34,7 +36,7 @@ $ sudo bash /tmp/installer.sh \
 --travis_build_images=focal
 ```
 
-## Restarting `travis-worker`
+## Restart the travis-worker
 
 After installation, or when configuration changes are applied to the worker, restart the worker as follows:
 
@@ -44,7 +46,7 @@ $ sudo systemctl restart travis-worker
 
 Worker configuration changes are applied on start.
 
-## Running Builds in the Focal Build Environment
+## Run Builds in the Focal Build Environment
 
 To run a project's builds in the new Focal build environment, please add a `dist: focal` to your `.travis.yml` file.
 

user/enterprise/high-availability.md

@@ -8,13 +8,13 @@ layout: en_enterprise
 
 Travis CI Enterprise (TCIE) 3.x typically runs in **a Kubernetes cluster** with one or multiple workers. Services are split into several pods in the cluster. This enables a High Availability setup out of the box which you are able to customize based on your needs.
 
-### Installing the Platform in High Availability Mode
+### Install the Platform in High Availability Mode
 
 Please make sure to configure your [Kubernetes](https://kubernetes.io/) cluster with redundant pods for each service and secure appropriate resources and configuration (see below) to run it or choosing to self-host several services. You will need to modify several services configuration on your own to achieve High Availability adjusted to your requirements.
 
 Select one of the options depending on your planned setup, deployment, data backup policies, the volume of users, and the number of build jobs. See also the regular [installation instructions for TCIE 3.x](/user/enterprise/tcie-3.x-setting-up-travis-ci-enterprise/#1-setting-up-enterprise-platform).
 
-#### Self hosting services for High Availability Mode
+#### Self-hosting services for High Availability Mode
 
 You may need to consider self-hosting of
 
@@ -25,9 +25,9 @@ Once TCIE 3.x is installed, go to the Dashboard, Configs and format *self-hosted
 
 ![Self-hosted config example](/images/tcie-3.x-self-hosted-db.png)
 
-Similar configuration options are available for self-hosted logs, Insights, Redis and Rabbit MQ. The self-hosted solution for these services allows you to fully deploy and configure their High Availability compliant setup as per your requirements.
+Similar configuration options are available for self-hosted logs, Insights, Redis, and Rabbit MQ. The self-hosted solution for these services allows you to fully deploy and configure their High-Availability compliant setup as per your requirements.
 
-#### Utilizing services in Kubernetes cluster
+#### Kubernetes cluster services
 
 Another option is to modify the configuration for the aforementioned services (PostgreSQL, Redis, and RabbitMQ) taking into account service specific details. These details can be found in the documentation for the tools. Since there are multiple possible variations, we suggest only general guidelines that should be treated as a starting point for developing your specific High Availability configuration.
 
@@ -47,7 +47,7 @@ Travis CI Enterprise 2.x typically runs as a single container instance communica
 
 If you're interested, or might be interested, in running Travis CI Enterprise in High Availability mode, please email us at [[email protected]](mailto:enterprise@travis-cicom?subject:HA%20Mode) and we can discuss options and help you get started.
 
-### Overview of Installation
+### Installation Overview
 
 The platform installation is similar to the standard [Enterprise installation](/user/enterprise/setting-up-travis-ci-enterprise/#1-setting-up-enterprise-platform-virtual-machine), and the [worker installation](#installing-the-worker-in-high-availability-mode) is identical. However, there are some additional [system prerequisites](/user/enterprise/high-availability/), which means that to install in HA mode, you will need the following:
  * 3+ **16 gigs of RAM, 8 CPUs, 40GB HDD**, i.e. `c4.2xlarge` with a 40GB HDD. - 2+ for the VMs running the Platform, and 1+ for the VMs running the Worker
@@ -56,7 +56,7 @@ and [Postgres](https://www.postgresql.org/) instances
  * [GitHub OAuth app](/user/enterprise/setting-up-travis-ci-enterprise/#prerequisites), [trial license](/user/enterprise/setting-up-travis-ci-enterprise/#prerequisites) -- enabled for HA
  * Internet connection -- note, this installation is _not_ airgapped by default. Let [us know](mailto:[email protected]) if you are interested in one.
 
-### Installing the Platform in High Availability Mode
+### Install the Platform in High Availability Mode
 
 HA is configured entirely on the Enterprise platform instance, but installing an HA platform is quite similar to installing a standard platform. The steps for HA are as follows.
 
@@ -76,15 +76,15 @@ HA is configured entirely on the Enterprise platform instance, but installing an
 
 Once your first platform instance is fully configured, you should be able to see the UI and request a build - your build will only run correctly, if a worker is installed. Try out your new platform, and [please let us know](mailto:[email protected]?subject=HA%20Troubleshooting) if you have questions.
 
-#### Adding More Platform Installations
+#### Add more Platform Installations
 
 We recommend at least two Platform containers for HA mode and you can install more Enterprise containers in the same way you [installed](/user/enterprise/setting-up-travis-ci-enterprise/#1-setting-up-enterprise-platform-virtual-machine) the first.
 
 Once your second platform is installed, it will also need its HA settings configured. Go to the Admin Dashboard for your new platform container at `https://<your-second-travis-ci-enterprise-domain>:8800` to configure these as you did for [the first platform installation](#installing-the-platform-in-high-availability-mode).
 
 
 
-## Installing the Worker in High Availability Mode (all versions)
+## Install the Worker in High Availability Mode (all versions)
 
 The worker installation works the same as for non-HA installations, as do the build environment compatibility defaults per Enterprise version. Check out the docs for which version of Enterprise handle different OS's([TCIE 2.x](/user/enterprise/setting-up-travis-ci-enterprise/#2-setting-up-the-enterprise-worker-virtual-machine) or [TCIE 3.x](/user/enterprise/tcie-3.x-setting-up-travis-ci-enterprise/#2-setting-up-the-enterprise-worker-virtual-machine) and other information regarding the installation. You will need to retrieve your RabbitMQ password from your own installation, rather than from the Travis CI Enterprise Admin Dashboard.