From fba1ccc7e20bdfd75f698eb3499be15e55024a2e Mon Sep 17 00:00:00 2001 From: Matthew Wildman Date: Thu, 24 Aug 2023 09:33:00 -0400 Subject: [PATCH] Misc fixes (2023-08-22) (#6562) * Fixed data center spelling and fixed apt- command * Added missing word --- .../salt/automate-a-static-site-deployment-with-salt/index.md | 2 +- .../terraform/create-a-nodebalancer-with-terraform/index.md | 4 ++-- .../install-cassandra-across-multiple-data-centers/index.md | 2 +- .../backing-up-gitlab-on-linode-object-storage/index.md | 2 +- .../linode-platform/dhcp-ip-address-reference/index.md | 4 ++-- .../linux-essentials/multi-cloud-vs-hybrid-cloud/index.md | 2 +- .../dns-manager/guides/incoming-dns-zone-transfers/index.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/guides/applications/configuration-management/salt/automate-a-static-site-deployment-with-salt/index.md b/docs/guides/applications/configuration-management/salt/automate-a-static-site-deployment-with-salt/index.md index 2c3bbc9741b..ff4f2a33ba9 100644 --- a/docs/guides/applications/configuration-management/salt/automate-a-static-site-deployment-with-salt/index.md +++ b/docs/guides/applications/configuration-management/salt/automate-a-static-site-deployment-with-salt/index.md @@ -125,7 +125,7 @@ master: 192.0.2.2 {{}} {{< note respectIndent=false >}} -Linode does not charge for traffic within a datacenter across private IP addresses. If your Salt master and minion are in the same datacenter, and both have a private IP addresses, you can use your Salt master's private IP address in this step to avoid incurring data traffic charges. +Linode does not charge for traffic within a data center across private IP addresses. If your Salt master and minion are in the same data center, and both have a private IP addresses, you can use your Salt master's private IP address in this step to avoid incurring data traffic charges. {{< /note >}} 1. Restart Salt on the minion: diff --git a/docs/guides/applications/configuration-management/terraform/create-a-nodebalancer-with-terraform/index.md b/docs/guides/applications/configuration-management/terraform/create-a-nodebalancer-with-terraform/index.md index d0d5216ec50..50febfe1fb0 100644 --- a/docs/guides/applications/configuration-management/terraform/create-a-nodebalancer-with-terraform/index.md +++ b/docs/guides/applications/configuration-management/terraform/create-a-nodebalancer-with-terraform/index.md @@ -247,7 +247,7 @@ resource "random_string" "password" { In addition to the variables you defined above, there is also a `random_string` resource with the label `password`. This resource is provided by the [Random provider](https://www.terraform.io/docs/providers/random/index.html), and will generate a random string of 32 characters, including uppercase characters, lowercase characters, and numbers. This string will be the root password for your backend Nodes. If you would rather have exact control over your passwords, you can define a password here in `variables.tf` and set the value for that password in `terraform.tfvars` in the next step. -1. Create the `terraform.tfvars` file and supply values for the `token`, `region`, and `node_count` variables. This example uses the `us-east` regional datacenter, and the `node_count` is two. +1. Create the `terraform.tfvars` file and supply values for the `token`, `region`, and `node_count` variables. This example uses the `us-east` data center and the `node_count` is two. {{< file "terraform.tfvars" >}} token = "your_api_token" @@ -261,7 +261,7 @@ node_count = 2 If you want to use an input variable's default value defined in the `variables.tf` file, you can omit providing a value for that variable in the `terraform.tfvars` file. {{< /note >}} - Feel free to change any of the values in the `terraform.tfvars` file to your liking. For a list of regional datacenter IDs, you can use the cURL command to query the API: + Feel free to change any of the values in the `terraform.tfvars` file to your liking. For a list of data center IDs, you can use the cURL command to query the API: curl https://api.linode.com/v4/regions diff --git a/docs/guides/databases/cassandra/install-cassandra-across-multiple-data-centers/index.md b/docs/guides/databases/cassandra/install-cassandra-across-multiple-data-centers/index.md index 500f1cbd757..83c76931041 100644 --- a/docs/guides/databases/cassandra/install-cassandra-across-multiple-data-centers/index.md +++ b/docs/guides/databases/cassandra/install-cassandra-across-multiple-data-centers/index.md @@ -82,7 +82,7 @@ To install Cassandra, follow these steps. Unless otherwise specified, execute th 1. Ensure the system is up to date. Reboot the system if necessary: ```command - sudo apt- update -y && sudo apt upgrade -y + sudo apt update -y && sudo apt upgrade -y ``` 1. Cassandra requires the use of a Java runtime. There are several different versions of Java to choose from, including OpenJDK and Oracle Java. This guide uses OpenJDK 11. Install OpenJDK using `apt`: diff --git a/docs/guides/development/version-control/backing-up-gitlab-on-linode-object-storage/index.md b/docs/guides/development/version-control/backing-up-gitlab-on-linode-object-storage/index.md index a8d637c8a70..66fe9cfea53 100644 --- a/docs/guides/development/version-control/backing-up-gitlab-on-linode-object-storage/index.md +++ b/docs/guides/development/version-control/backing-up-gitlab-on-linode-object-storage/index.md @@ -51,7 +51,7 @@ The following chart will explain each configuration settings in additional detai | ------------| --------------------- | | provider | AWS (The provider must be set to AWS because it is dependent on [s3cmd](/docs/products/storage/object-storage/guides/s3cmd/)) | | region | The region the bucket was created in. A full list of regions can be found in the [Product Documentation](/docs/products/storage/object-storage/). | -| endpoint | The endpoint url for the datacenter. Uses the syntax of **region.linodeobjects.com** | +| endpoint | The endpoint url for the data center. Uses the syntax of **region.linodeobjects.com** | | aws_access_key-id | The Object Storage [Access Key](/docs/products/storage/object-storage/guides/access-keys/) created in a previous step. | | aws_secret_access_key | The Object Storage [Secret Key](/docs/products/storage/object-storage/guides/access-keys/) created in a previous step. | | gitlab_rails['backup_upload_remote_directory'] | The [label](/docs/products/storage/object-storage/get-started/#create-a-bucket) of the bucket created during bucket creation. diff --git a/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md b/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md index c8a0d7aba19..c8040c01b9b 100644 --- a/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md +++ b/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md @@ -1,6 +1,6 @@ --- slug: dhcp-ip-address-reference -description: 'Shortguide that displays a list of all IP addresses used for configurations that rely on DHCP by their datacenter.' +description: 'Shortguide that displays a list of all IP addresses used for configurations that rely on DHCP by their data center.' license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' modified: 2021-09-10 modified_by: @@ -13,7 +13,7 @@ aliases: ['/quick-answers/linode-platform/dhcp-ip-address-reference/'] authors: ["Linode"] --- -In some cases, such as when configuring a firewall, you may need to know the IP addresses that Linode uses for our DHCP servers. Below is a list of all DHCP IP addresses categorized by their datacenter, to assist in any configuration you may need. +In some cases, such as when configuring a firewall, you may need to know the IP addresses that Linode uses for our DHCP servers. Below is a list of all DHCP IP addresses categorized by their data center, to assist in any configuration you may need. ## Fremont diff --git a/docs/guides/quick-answers/linux-essentials/multi-cloud-vs-hybrid-cloud/index.md b/docs/guides/quick-answers/linux-essentials/multi-cloud-vs-hybrid-cloud/index.md index 79244f7aa25..22336938c64 100644 --- a/docs/guides/quick-answers/linux-essentials/multi-cloud-vs-hybrid-cloud/index.md +++ b/docs/guides/quick-answers/linux-essentials/multi-cloud-vs-hybrid-cloud/index.md @@ -38,7 +38,7 @@ Hybrid cloud computing is more complicated than multicloud for two reasons: - You must include a private cloud option. - You must be able to seamlessly combine both private and public options. -For example, you have a service that you run on-premise. It's a containerized application, run via a private cloud, and your container database is served up via your in-house datacenter. That application runs well during non-peak periods. But during peak demand, your private cloud isn't capable of scaling to meet the higher demand. +For example, you have a service that you run on-premise. It's a containerized application, run via a private cloud, and your container database is served up via your in-house data center. That application runs well during non-peak periods. But during peak demand, your private cloud isn't capable of scaling to meet the higher demand. To make that work, you employ frameworks and services that automatically shift the load from your in-house private cloud to your public cloud to handle the added demand. Once peak times end, the load shifts back to your private cloud. diff --git a/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md b/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md index fbaa69c00ca..5947459400f 100644 --- a/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md +++ b/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md @@ -87,6 +87,6 @@ As part of this, a common reason for using Linode's DNS Manager as a secondary D 1. Click the **Create Domain** button to create the domain zone and start the transfer. -1. Once the DNS zone transfer is finished, update the authoritative name servers on your domain's registrar to use some or all of Linode's name servers (ns1.linode.com through ns5.linode.com). If desired, add them alongside your current DNS provider's name servers (so Linode operates as one of many name servers) or you can delete their name servers (so Linode the only authoritative name server). +1. Once the DNS zone transfer is finished, update the authoritative name servers on your domain's registrar to use some or all of Linode's name servers (ns1.linode.com through ns5.linode.com). If desired, add them alongside your current DNS provider's name servers (so Linode operates as one of many name servers) or you can delete their name servers (so Linode is the only authoritative name server). Linode checks for DNS changes when the refresh time elapses for the domain *or* when it receives a NOTIFY request from one of the designated external name servers. \ No newline at end of file