Fix typos, formatting

Author: Blargian

docs/en/about-us/cloud.md

@@ -25,6 +25,6 @@ Some of the benefits of using ClickHouse Cloud are described below:
 
 Clickhouse Cloud continuously upgrades your service to a newer version. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.
 
-We offer a "Fast" Release Channel for subscribing to updates ahead of the regular release schedule. Access to early upgrades is recommended only for non-production environments and can be requested by logging a support ticket.
+We offer a "Fast" Release Channel for subscribing to updates ahead of the regular release schedule. For more details, see ["Fast Release Channel"](../cloud/manage/upgrades.md/#fast-release-channel-early-upgrades).
 
 If you rely on functionality in the earlier version, you can, in some cases, revert to the previous behavior using your service's compatibility setting.

docs/en/cloud/get-started/cloud-quick-start.md

@@ -89,7 +89,7 @@ That's it - you are ready to start using your new ClickHouse service!
 
 ## 3. Create a database and table
 
-Like most database management systems, ClickHouse logically groups tables into **databases**. Use the `CREATE DATABASE` command to create a new database in ClickHouse:
+Like most database management systems, ClickHouse logically groups tables into **databases**. Use the [`CREATE DATABASE`](../../sql-reference/statements/create/database.md) command to create a new database in ClickHouse:
 
 ```sql
 CREATE DATABASE IF NOT EXISTS helloworld
@@ -109,20 +109,20 @@ ENGINE = MergeTree()
 PRIMARY KEY (user_id, timestamp)
 ```
 
-In the example above, `my_first_table` is a MergeTree table with four columns:
+In the example above, `my_first_table` is a [`MergeTree`](../../engines/table-engines/mergetree-family/mergetree.md) table with four columns:
 
-  - `user_id`:  a 32-bit unsigned integer
-  - `message`: a String data type, which replaces types like VARCHAR, BLOB, CLOB and others from other database systems
-  - `timestamp`: a DateTime value, which represents an instant in time
-  - `metric`: a 32-bit floating point number
+  - `user_id`:  a 32-bit unsigned integer ([UInt32](../../sql-reference/data-types/int-uint.md))
+  - `message`: a [String](../../sql-reference/data-types/string.md) data type, which replaces types like `VARCHAR`, `BLOB`, `CLOB` and others from other database systems
+  - `timestamp`: a [DateTime](../../sql-reference/data-types/datetime.md) value, which represents an instant in time
+  - `metric`: a 32-bit floating point number ([Float32](../../sql-reference/data-types/float.md))
 
-:::note table engines
-The table engine determines:
-  - How and where the data is stored
+:::note Table engines
+Table engines determine:
+  - How and where data is stored
   - Which queries are supported
   - Whether or not the data is replicated
-
-There are many engines to choose from, but for a simple table on a single-node ClickHouse server, [MergeTree](/en/engines/table-engines/mergetree-family/mergetree.md) is your likely choice.
+<br/>
+There are many table engines to choose from, but for a simple table on a single-node ClickHouse server, [`MergeTree`](/en/engines/table-engines/mergetree-family/mergetree.md) is your likely choice.
 :::
 
 ### 3a. A Brief Intro to Primary Keys
@@ -143,9 +143,11 @@ then the key becomes the tuple specified in the `ORDER BY` clause. If you specif
 The primary key is also the sorting key, which is a tuple of `(user_id, timestamp)`.  Therefore, the data stored in each
 column file will be sorted by `user_id`, then `timestamp`.
 
+For a deep dive into core ClickHouse concepts, see ["Core Concepts"](../../managing-data/core-concepts/index.md).
+
 ## 4. Insert Data
 
-You can use the familiar `INSERT INTO TABLE` command with ClickHouse, but it is important to understand that each insert into a `MergeTree` table causes a **part** to be created in storage.
+You can use the familiar [`INSERT INTO TABLE`](../../sql-reference/statements/insert-into.md) command with ClickHouse, but it is important to understand that each insert into a [`MergeTree`](/en/engines/table-engines/mergetree-family/mergetree.md) table causes a **part** to be created in storage.
 
 :::tip ClickHouse best practice
 Insert a large number of rows per batch - tens of thousands or even millions of
@@ -165,7 +167,7 @@ INSERT INTO helloworld.my_first_table (user_id, message, timestamp, metric) VALU
 ```
 
 :::note
-Notice the `timestamp` column is populated using various **Date** and **DateTime** functions. ClickHouse has hundreds of useful functions that you can [view in the **Functions** section](/docs/en/sql-reference/functions/).
+Notice the `timestamp` column is populated using various [**Date**](../../sql-reference/data-types/date.md) and [**DateTime**](../../sql-reference/data-types/datetime.md) functions. ClickHouse has hundreds of useful functions that you can [view in the **Functions** section](/docs/en/sql-reference/functions/).
 :::
 
 Let's verify it worked:
@@ -223,7 +225,7 @@ Notice the response comes back in a nice table format:
 4 rows in set. Elapsed: 0.008 sec.
 ```
 
-4. Add a `FORMAT` clause to specify one of the [many supported output formats of ClickHouse](/en/interfaces/formats/):
+4. Add a [`FORMAT`](../../sql-reference/statements/select/format.md) clause to specify one of the [many supported output formats of ClickHouse](/en/interfaces/formats/):
 
 <br/>
 
@@ -261,7 +263,7 @@ the timestamp of the event.
 
 Suppose we have the following text in a CSV file named `data.csv`:
 
-```bash
+```bash title="data.csv"
 102,This is data in a file,2022-02-22 10:43:28,123.45
 101,It is comma-separated,2022-02-23 00:00:00,456.78
 103,Use FORMAT to specify the format,2022-02-21 10:43:30,678.90

docs/en/cloud/get-started/sql-console.md

@@ -42,11 +42,15 @@ The Cell Inspector tool can be used to view large amounts of data contained with
 
 ### Sorting a table
 
-To sort a table in the SQL console, open a table and select the ‘Sort’ button in the toolbar. This button will open a menu that will allow you to configure your sort. You can choose a column by which to sort and configure the ordering of the sort (ascending or descending). Select ‘Apply’ or press Enter to sort your table
+To sort a table in the SQL console, open a table and select the ‘Sort’ button in the toolbar. This button will open a menu that will allow you to configure your sort. You can choose a column by which you want to sort and configure the ordering of the sort (ascending or descending). Select ‘Apply’ or press Enter to sort your table
 
 ![sort descending on a column](@site/docs/en/cloud/images/sqlconsole/sort-descending-on-column.png)
 
-The SQL console also allows you to add multiple sorts to a table. Click the ‘Sort’ button again to add another sort. Note: sorts are applied in the order that they appear in the sort pane (top to bottom). To remove a sort, simply click the ‘x’ button next to the sort.
+The SQL console also allows you to add multiple sorts to a table. Click the ‘Sort’ button again to add another sort. 
+
+:::note
+Sorts are applied in the order that they appear in the sort pane (top to bottom). To remove a sort, simply click the ‘x’ button next to the sort.
+:::
 
 ### Filtering a table
 

docs/en/cloud/manage/backups.md

@@ -18,7 +18,7 @@ ClickHouse Cloud backups are a combination of "full" and "incremental" backups t
 
 In the screenshot below, the solid line squares show full backups and the dotted line squares show incremental backups. The solid line rectangle around the squares denotes the retention period and the backups that are visible to the end user, which can be used for a backup restore. In the scenario below, backups are being taken every 24 hours and are retained for 2 days.
 
-On Day 1, a full backup is taken to start the backup chain. On Day 2, an incremental backup is taken and now we have a full and incremental backup available to restore from. By Day 7, we have one full backup and six incremental backups in the chain, with the most recent two incremental backups visible to the user. On Day 8, we take a new full backup, and on Day 9, once we have two backups in the new chain, the previous chain is discarded.
+On Day 1, a full backup is taken to start the backup chain. On Day 2, an incremental backup is taken, and we now have a full and incremental backup available to restore from. By Day 7, we have one full backup and six incremental backups in the chain, with the most recent two incremental backups visible to the user. On Day 8, we take a new full backup, and on Day 9, once we have two backups in the new chain, the previous chain is discarded.
 
 ![Backup chain](./images/backup-chain.png)
 
@@ -32,13 +32,13 @@ No free backups are included in the new pricing.
 
 ## Configurable backups
 
-<ScalePlanFeatureBadge feature="Configurable Backups"/>
+<ScalePlanFeatureBadge feature="Configurable Backups" linking_verb_are="True"/>
 
 ClickHouse Cloud allows you to configure the schedule for your backups for **Scale** and **Enterprise** tier services. Backups can be configured along the following dimensions based on your business needs.
 
-- **Retention**: Duration in days, for which each backup will be retained. Retention can be specified as low as 1 day, and as high as 30 days with several values to pick in between.
-- **Frequency**: Frequency allows you to specify the time duration between subsequent backups. For instance, a frequency of "every 12 hours" means that backups will be spaced 12 hours apart. Frequency can range from "every 6 hours" to "every 48 hours" in the following hourly increments: 6, 8, 12, 16, 20, 24, 36, 48.
-- **Start Time**: Start time for when you want to schedule backups each day. Specifying a start time implies that the backup "Frequency" will default to once every 24 hours.  Clickhouse Cloud will start the backup within an hour of the specified start time.
+- **Retention**: The duration of days, for which each backup will be retained. Retention can be specified as low as 1 day, and as high as 30 days with several values to pick in between.
+- **Frequency**: The frequency allows you to specify the time duration between subsequent backups. For instance, a frequency of "every 12 hours" means that backups will be spaced 12 hours apart. Frequency can range from "every 6 hours" to "every 48 hours" in the following hourly increments: `6`, `8`, `12`, `16`, `20`, `24`, `36`, `48`.
+- **Start Time**: The start time for when you want to schedule backups each day. Specifying a start time implies that the backup "Frequency" will default to once every 24 hours.  Clickhouse Cloud will start the backup within an hour of the specified start time.
 
 :::note
 The custom schedule will override the default backup policy in ClickHouse Cloud for your given service.
@@ -51,7 +51,7 @@ To configure the backup schedule for a service, go to the **Settings** tab in th
 </div>
 <br/>
 
-This opens a slideout where you can choose values for retention, frequency, and start time. You will need to save the chosen settings for them to take effect.
+This opens a tab to the right where you can choose values for retention, frequency, and start time. You will need to save the chosen settings for them to take effect.
 
 <div class="eighty-percent">
 ![Select backup retention and frequency](./images/backup-configuration-form.png)
@@ -63,12 +63,12 @@ Start time and frequency are mutually exclusive. Start time takes precedence.
 :::
 
 :::note
-Changing the backups schedule can cause higher monthly charges for storage as some of the backups might not be covered in the default backups for the service. See “Understanding backup cost” section below.
+Changing the backup schedule can cause higher monthly charges for storage as some of the backups might not be covered in the default backups for the service. See [“Understanding backup cost”](#understanding-backup-cost) section below.
 :::
 
 ## Backup status list
 
-Your service will be backed up based on the set schedule - whether it is the default daily schedule or a custom schedule picked by you. All available backups can be viewed from the **Backups** tab of the service. From here, you can see the status of the backup, the duration, as well as the size of the backup. You can also restore a specific backup using the **Actions** column.
+Your service will be backed up based on the set schedule, whether it is the default daily schedule or a custom schedule picked by you. All available backups can be viewed from the **Backups** tab of the service. From here, you can see the status of the backup, the duration, as well as the size of the backup. You can also restore a specific backup using the **Actions** column.
 
 ![List of backups statuses](./images/backup-status-list.png)
 
@@ -81,17 +81,17 @@ To understand the backup cost, you can view the backup cost per service from the
 ![Backup usage chart](./images/backup-usage.png)
 
 Estimating the total cost for your backups requires you to set a schedule. We are also working on updating our [pricing calculator](https://clickhouse.com/pricing), so you can get a monthly cost estimate before setting a schedule. You will need to provide the following inputs in order to estimate the cost:
-- Size of full and incremental backups
+- Size of the full and incremental backups
 - Desired frequency
 - Desired retention
 - Cloud provider and region
 
 :::note
-Keep in mind that the estimated cost for backups will change as the size of the data in the service changes (grows) over time.
+Keep in mind that the estimated cost for backups will change as the size of the data in the service grows over time.
 :::
 
 
-## Restore a backup​
+## Restore a backup
 
 Backups are restored to a new ClickHouse Cloud service, not to the existing service from which the backup was taken.
 
@@ -108,7 +108,7 @@ The new service will show in the services list as `Provisioning` until it is rea
 
 ## Working with your restored service
 
-After a backup has been restored, you will now have two similar services: the **original service** that needed to be restored, and a new **restored service** that was restored from a backup of the original.
+After a backup has been restored, you will now have two similar services: the **original service** that needed to be restored, and a new **restored service** that has been restored from a backup of the original.
 
 Once the backup restore is complete, you should do one of the following:
 - Use the new restored service and remove the original service.
@@ -118,17 +118,17 @@ Once the backup restore is complete, you should do one of the following:
 
 To use the new service, perform these steps:
 
-1. Verify that the new service has the IP Access List entries required by your use cases.
+1. Verify that the new service has the IP Access List entries required for your use case.
 1. Verify that the new service contains the data that you need.
 1. Remove the original service.
 
-### Migrate data from the **new restored service** back to the **original service**
+### Migrate data from the **newly restored service** back to the **original service**
 
-Suppose you cannot work with the newly restored service for any reason; for example, if you have users or applications that connect to the existing service. You may decide to migrate the newly restored data into the original service. The migration can be accomplished by following these steps:
+Suppose you cannot work with the newly restored service for some reason, for example, if you still have users or applications that connect to the existing service. You may decide to migrate the newly restored data into the original service. The migration can be accomplished by following these steps:
 
 **Allow remote access to the newly restored service**
 
-The new service should be restored from a backup with the same IP Allow List as the original service. This is required as connections will not be allowed to other ClickHouse Cloud services unless you had allowed access from **Anywhere**. Modify the allow list and allow access from **Anywhere** temporarily. See the [IP Access List](/docs/en/cloud/security/setting-ip-filters) docs for details.
+The new service should be restored from a backup with the same IP Allowlist as the original service. This is required as connections will not be allowed to other ClickHouse Cloud services unless you had allowed access from **Anywhere**. Modify the allowlist and allow access from **Anywhere** temporarily. See the [IP Access List](/docs/en/cloud/security/setting-ip-filters) docs for details.
 
 **On the newly restored ClickHouse service (the system that hosts the restored data)**
 
@@ -151,9 +151,9 @@ Add a read only user that can read the source table (`db.table` in this example)
 Copy the table definition:
 
   ```sql
-  select create_table_query
-  from system.tables
-  where database = 'db' and table = 'table'
+  SELECT create_table_query
+  FROM system.tables
+  WHERE database = 'db' AND table = 'table'
   ```
 
 **On the destination ClickHouse Cloud system (the one that had the damaged table):**
@@ -166,12 +166,11 @@ Create the destination database:
 Using the `CREATE TABLE` statement from the source, create the destination:
 
 :::tip
-Change the `ENGINE` to `ReplicatedMergeTree` without any parameters when you run the `CREATE` statement.  ClickHouse Cloud always replicates tables and provides the correct parameters.
+Change the `ENGINE` to `ReplicatedMergeTree` without any parameters when you run the `CREATE` statement. ClickHouse Cloud always replicates tables and provides the correct parameters.
 :::
 
   ```sql
   CREATE TABLE db.table ...
-  # highlight-next-line
   ENGINE = ReplicatedMergeTree
   ORDER BY ...
   ```

docs/en/cloud/manage/cloud-tiers.md

@@ -6,16 +6,18 @@ title: Service Types
 
 # ClickHouse Cloud Tiers
 
-There are several tiers available in ClickHouse Cloud. Tiers are assigned at any organizational level. Services within an organization therefore belong to the same tier. This page discusses which tiers is right for your specific use case.
+There are several tiers available in ClickHouse Cloud. 
+Tiers are assigned at any organizational level. Services within an organization therefore belong to the same tier.
+This page discusses which tiers are right for your specific use case.
 
 **Summary of cloud tiers:**
 
 <table><thead>
   <tr>
     <th></th>
-    <th>Basic</th>
-    <th>Scale (Recommended)</th>
-    <th>Enterprise</th>
+    <th>[Basic](#basic)</th>
+    <th>[Scale (Recommended)](#scale)</th>
+    <th>[Enterprise](#enterprise)</th>
   </tr></thead>
 <tbody>
   <tr>
@@ -106,8 +108,8 @@ There are several tiers available in ClickHouse Cloud. Tiers are assigned at any
   </tr>
   <tr>
     <td>SAML/SSO</td>
-    <td>✓</td>
-    <td>✓</td>
+    <td></td>
+    <td></td>
     <td>✓</td>
   </tr>
   <tr>
@@ -178,10 +180,10 @@ Designed for workloads requiring enhanced SLAs (2+ replica deployments), scalabi
 Caters to large-scale, mission critical deployments that have stringent security and compliance needs.
 
 - Everything in Scale, **plus**
-- Flexible scaling: standard profiles (1:4 vCPU:memory ratio), as well as `HighMemory (1:8 ratio)` and `HighCPU (1:2 ratio)` custom profiles.
+- Flexible scaling: standard profiles (`1:4 vCPU:memory ratio`), as well as `HighMemory (1:8 ratio)` and `HighCPU (1:2 ratio)` custom profiles.
 - Provides the highest levels of performance and reliability guarantees.
 - Supports enterprise-grade security:
-  - Single Sign On(SSO)
+  - Single Sign On (SSO)
   - Enhanced Encryption: For AWS and GCP services. Services are encrypted by our key by default and can be rotated to their key to enable Customer Managed Encryption Keys (CMEK).
 - Allows Scheduled upgrades: Users can select the day of the week/time window for upgrades, both database and cloud releases.  
 - Offers [HIPAA](../security/compliance-overview.md/#hipaa) Compliance.