ClickHouse · blinkov · Mar 21, 2020 · Mar 19, 2020 · Mar 19, 2020 · Mar 19, 2020
diff --git a/docs/dscr-templates/template-function.md b/docs/dscr-templates/template-function.md
@@ -4,7 +4,7 @@ Short description.
 
 **Syntax** (without SELECT)
 
-```sql
+``` sql
 <function syntax>
 ```
 
@@ -14,12 +14,12 @@ More text (Optional).
 
 **Parameters** (Optional)
 
-- `x` — Description. [Type name](relative/path/to/type/dscr.md#type).
-- `y` — Description. [Type name](relative/path/to/type/dscr.md#type).
+-   `x` — Description. [Type name](relative/path/to/type/dscr.md#type).
+-   `y` — Description. [Type name](relative/path/to/type/dscr.md#type).
 
 **Returned value(s)**
 
-- Returned values list.
+-   Returned values list.
 
 Type: [Type](relative/path/to/type/dscr.md#type).
 
@@ -29,20 +29,19 @@ The example must show usage and/or a use cases. The following text contains reco
 
 Input table (Optional):
 
-```text
+``` text
 ```
 
 Query:
 
-```sql
+``` sql
 ```
 
 Result:
 
-```text
+``` text
 ```
 
 **See Also** (Optional)
 
-- [link](#)
-
+-   [link](#)
diff --git a/docs/dscr-templates/template-setting.md b/docs/dscr-templates/template-setting.md
@@ -2,19 +2,19 @@
 
 Description.
 
-For switcher setting, use the typical phrase: "Enables or disables something ...".
+For switcher setting, use the typical phrase: “Enables or disables something …”.
 
 Possible values:
 
 *For switcher setting:*
 
-- 0 — Disabled.
-- 1 — Enabled.
+-   0 — Disabled.
+-   1 — Enabled.
 
 *For another setting (typical phrases):*
 
-- Positive integer.
-- 0 — Disabled or unlimited or smth. else.
+-   Positive integer.
+-   0 — Disabled or unlimited or smth. else.
 
 Default value: `value`.
 
@@ -24,4 +24,4 @@ The name of additional section can be any, for example **Usage**.
 
 **See Also** (Optional)
 
-- [link](#)
+-   [link](#)
diff --git a/docs/dscr-templates/template-system-table.md b/docs/dscr-templates/template-system-table.md
@@ -1,21 +1,21 @@
-## system.table_name {#system_tables-table_name}
+## system.table\_name {#system-tables-table-name}
 
 Description.
 
 Columns:
 
-- `column_name` ([data_type_name](data_type_uri)) — Description.
+-   `column_name` ([data\_type\_name](data_type_uri)) — Description.
 
 **Example**
 
-```sql
+``` sql
 SELECT * FROM system.table_name
 ```
 
-```text
+``` text
 Some output. It shouldn't be long.
 ```
 
 **See Also**
 
-- [Article name](uri) — Some words about referenced information.
+-   [Article name](uri) — Some words about referenced information.
diff --git a/docs/dscr-templates/template-table-engine.md b/docs/dscr-templates/template-table-engine.md
@@ -1,51 +1,49 @@
-# EngineName
+# EngineName {#enginename}
 
-- What the engine does.
-- Relations with other engines if they exist.
+-   What the engine does.
+-   Relations with other engines if they exist.
 
-## Creating a Table
+## Creating a Table {#creating-a-table}
 
-```
-Syntax codeblock
-```
+    Syntax codeblock
 
 **Engine Parameters**
 
 **Query Clauses**
 
-
-## Virtual columns
+## Virtual columns {#virtual-columns}
 
 If they exist.
 
-## Specifics and recommendations
+## Specifics and recommendations {#specifics-and-recommendations}
+
 Algorithms
 Specifics of read/write processes
 Examples of tasks
 Recommendations for usage
 Specifics of data storage
 
-## Usage Example
+## Usage Example {#usage-example}
 
 The example must show usage and/or a use cases. The following text contains recommended parts of an example.
 
 Input table:
 
-```text
+``` text
 ```
 
 Query:
 
-```sql
+``` sql
 ```
 
 Result:
 
-```text
+``` text
 ```
 
 Any text clarifying the example.
 
-## See Also
+## See Also {#see-also}
 
-- [link](#)
+-   [link](#)
diff --git a/docs/en/changelog/2017.md b/docs/en/changelog/2017.md
diff --git a/docs/en/changelog/2018.md b/docs/en/changelog/2018.md
diff --git a/docs/en/changelog/2019.md b/docs/en/changelog/2019.md
diff --git a/docs/en/commercial/cloud.md b/docs/en/commercial/cloud.md
@@ -7,8 +7,8 @@
 
 [Yandex Managed Service for ClickHouse](https://cloud.yandex.com/services/managed-clickhouse?utm_source=referrals&utm_medium=clickhouseofficialsite&utm_campaign=link3) provides the following key features:
 
-- Fully managed ZooKeeper service for [ClickHouse replication](../operations/table_engines/replication.md)
-- Multiple storage type choices
-- Replicas in different availability zones
-- Encryption and isolation
-- Automated maintenance
+-   Fully managed ZooKeeper service for [ClickHouse replication](../operations/table_engines/replication.md)
+-   Multiple storage type choices
+-   Replicas in different availability zones
+-   Encryption and isolation
+-   Automated maintenance
diff --git a/docs/en/data_types/array.md b/docs/en/data_types/array.md
@@ -1,4 +1,4 @@
-# Array(T) {#data_type-array}
+# Array(T) {#data-type-array}
 
 Array of `T`-type items.
 

diff --git a/docs/en/data_types/datetime.md b/docs/en/data_types/datetime.md
@@ -1,4 +1,4 @@
-# DateTime {#data_type-datetime}
+# DateTime {#data-type-datetime}
 
 Allows to store an instant in time, that can be expressed as a calendar date and a time of a day.
 
@@ -54,8 +54,8 @@ SELECT * FROM dt;
 └─────────────────────┴──────────┘
 ```
 
-- When inserting datetime as an integer, it is treated as Unix Timestamp (UTC). `1546300800` represents `'2019-01-01 00:00:00'` UTC. However, as `timestamp` column has `Europe/Moscow` (UTC+3) timezone specified, when outputting as string the value will be shown as `'2019-01-01 03:00:00'`
-- When inserting string value as datetime, it is treated as being in column timezone. `'2019-01-01 00:00:00'` will be treated as being in `Europe/Moscow` timezone and saved as `1546290000`.
+-   When inserting datetime as an integer, it is treated as Unix Timestamp (UTC). `1546300800` represents `'2019-01-01 00:00:00'` UTC. However, as `timestamp` column has `Europe/Moscow` (UTC+3) timezone specified, when outputting as string the value will be shown as `'2019-01-01 03:00:00'`
+-   When inserting string value as datetime, it is treated as being in column timezone. `'2019-01-01 00:00:00'` will be treated as being in `Europe/Moscow` timezone and saved as `1546290000`.
 
 **2.** Filtering on `DateTime` values
 
@@ -111,12 +111,12 @@ FROM dt
 
 ## See Also {#see-also}
 
-- [Type conversion functions](../query_language/functions/type_conversion_functions.md)
-- [Functions for working with dates and times](../query_language/functions/date_time_functions.md)
-- [Functions for working with arrays](../query_language/functions/array_functions.md)
-- [The `date_time_input_format` setting](../operations/settings/settings.md#settings-date_time_input_format)
-- [The `timezone` server configuration parameter](../operations/server_settings/settings.md#server_settings-timezone)
-- [Operators for working with dates and times](../query_language/operators.md#operators-datetime)
-- [The `Date` data type](date.md)
+-   [Type conversion functions](../query_language/functions/type_conversion_functions.md)
+-   [Functions for working with dates and times](../query_language/functions/date_time_functions.md)
+-   [Functions for working with arrays](../query_language/functions/array_functions.md)
+-   [The `date_time_input_format` setting](../operations/settings/settings.md#settings-date_time_input_format)
+-   [The `timezone` server configuration parameter](../operations/server_settings/settings.md#server_settings-timezone)
+-   [Operators for working with dates and times](../query_language/operators.md#operators-datetime)
+-   [The `Date` data type](date.md)
 
 [Original article](https://clickhouse.tech/docs/en/data_types/datetime/) <!--hide-->
diff --git a/docs/en/data_types/datetime64.md b/docs/en/data_types/datetime64.md
@@ -1,4 +1,4 @@
-# DateTime64 {#data_type-datetime64}
+# DateTime64 {#data-type-datetime64}
 
 Allows to store an instant in time, that can be expressed as a calendar date and a time of a day, with defined sub-second precision
 
@@ -40,8 +40,8 @@ SELECT * FROM dt
 └─────────────────────────┴──────────┘
 ```
 
-- When inserting datetime as an integer, it is treated as an appropriately scaled Unix Timestamp (UTC). `1546300800000` (with precision 3) represents `'2019-01-01 00:00:00'` UTC. However, as `timestamp` column has `Europe/Moscow` (UTC+3) timezone specified, when outputting as a string the value will be shown as `'2019-01-01 03:00:00'`
-- When inserting string value as datetime, it is treated as being in column timezone. `'2019-01-01 00:00:00'` will be treated as being in `Europe/Moscow` timezone and stored as `1546290000000`.
+-   When inserting datetime as an integer, it is treated as an appropriately scaled Unix Timestamp (UTC). `1546300800000` (with precision 3) represents `'2019-01-01 00:00:00'` UTC. However, as `timestamp` column has `Europe/Moscow` (UTC+3) timezone specified, when outputting as a string the value will be shown as `'2019-01-01 03:00:00'`
+-   When inserting string value as datetime, it is treated as being in column timezone. `'2019-01-01 00:00:00'` will be treated as being in `Europe/Moscow` timezone and stored as `1546290000000`.
 
 **2.** Filtering on `DateTime64` values
 
@@ -87,11 +87,11 @@ FROM dt
 
 ## See Also {#see-also}
 
-- [Type conversion functions](../query_language/functions/type_conversion_functions.md)
-- [Functions for working with dates and times](../query_language/functions/date_time_functions.md)
-- [Functions for working with arrays](../query_language/functions/array_functions.md)
-- [The `date_time_input_format` setting](../operations/settings/settings.md#settings-date_time_input_format)
-- [The `timezone` server configuration parameter](../operations/server_settings/settings.md#server_settings-timezone)
-- [Operators for working with dates and times](../query_language/operators.md#operators-datetime)
-- [`Date` data type](date.md)
-- [`DateTime` data type](datetime.md)
+-   [Type conversion functions](../query_language/functions/type_conversion_functions.md)
+-   [Functions for working with dates and times](../query_language/functions/date_time_functions.md)
+-   [Functions for working with arrays](../query_language/functions/array_functions.md)
+-   [The `date_time_input_format` setting](../operations/settings/settings.md#settings-date_time_input_format)
+-   [The `timezone` server configuration parameter](../operations/server_settings/settings.md#server_settings-timezone)
+-   [Operators for working with dates and times](../query_language/operators.md#operators-datetime)
+-   [`Date` data type](date.md)
+-   [`DateTime` data type](datetime.md)
diff --git a/docs/en/data_types/decimal.md b/docs/en/data_types/decimal.md
@@ -4,8 +4,8 @@ Signed fixed-point numbers that keep precision during add, subtract and multiply
 
 ## Parameters {#parameters}
 
-- P - precision. Valid range: \[ 1 : 38 \]. Determines how many decimal digits number can have (including fraction).
-- S - scale. Valid range: \[ 0 : P \]. Determines how many decimal digits fraction can have.
+-   P - precision. Valid range: \[ 1 : 38 \]. Determines how many decimal digits number can have (including fraction).
+-   S - scale. Valid range: \[ 0 : P \]. Determines how many decimal digits fraction can have.
 
 Depending on P parameter value Decimal(P, S) is a synonym for:
 - P from \[ 1 : 9 \] - for Decimal32(S)
@@ -14,9 +14,9 @@ Depending on P parameter value Decimal(P, S) is a synonym for:
 
 ## Decimal value ranges {#decimal-value-ranges}
 
-- Decimal32(S) - ( -1 \* 10^(9 - S), 1 \* 10^(9 - S) )
-- Decimal64(S) - ( -1 \* 10^(18 - S), 1 \* 10^(18 - S) )
-- Decimal128(S) - ( -1 \* 10^(38 - S), 1 \* 10^(38 - S) )
+-   Decimal32(S) - ( -1 \* 10^(9 - S), 1 \* 10^(9 - S) )
+-   Decimal64(S) - ( -1 \* 10^(18 - S), 1 \* 10^(18 - S) )
+-   Decimal128(S) - ( -1 \* 10^(38 - S), 1 \* 10^(38 - S) )
 
 For example, Decimal32(4) can contain numbers from -99999.9999 to 99999.9999 with 0.0001 step.
 
@@ -30,15 +30,15 @@ Because modern CPU’s do not support 128-bit integers natively, operations on D
 
 Binary operations on Decimal result in wider result type (with any order of arguments).
 
-- Decimal64(S1) <op> Decimal32(S2) -\> Decimal64(S)
-- Decimal128(S1) <op> Decimal32(S2) -\> Decimal128(S)
-- Decimal128(S1) <op> Decimal64(S2) -\> Decimal128(S)
+-   Decimal64(S1) <op> Decimal32(S2) -\> Decimal64(S)
+-   Decimal128(S1) <op> Decimal32(S2) -\> Decimal128(S)
+-   Decimal128(S1) <op> Decimal64(S2) -\> Decimal128(S)
 
 Rules for scale:
 
-- add, subtract: S = max(S1, S2).
-- multuply: S = S1 + S2.
-- divide: S = S1.
+-   add, subtract: S = max(S1, S2).
+-   multuply: S = S1 + S2.
+-   divide: S = S1.
 
 For similar operations between Decimal and integers, the result is Decimal of the same size as an argument.
 

diff --git a/docs/en/data_types/domains/ipv4.md b/docs/en/data_types/domains/ipv4.md
@@ -58,9 +58,9 @@ If you want to convert `IPv4` value to a string, you have to do that explicitly
 SELECT toTypeName(s), IPv4NumToString(from) as s FROM hits LIMIT 1;
 ```
 
-  ┌─toTypeName(IPv4NumToString(from))─┬─s──────────────┐
-  │ String                            │ 183.247.232.58 │
-  └───────────────────────────────────┴────────────────┘
+    ┌─toTypeName(IPv4NumToString(from))─┬─s──────────────┐
+    │ String                            │ 183.247.232.58 │
+    └───────────────────────────────────┴────────────────┘
 
 Or cast to a `UInt32` value:
 

diff --git a/docs/en/data_types/domains/overview.md b/docs/en/data_types/domains/overview.md
@@ -4,23 +4,23 @@ Domains are special-purpose types, that add some extra features atop of existing
 
 You can use domains anywhere corresponding base type can be used:
 
-- Create a column of domain type
-- Read/write values from/to domain column
-- Use it as index if base type can be used as index
-- Call functions with values of domain column
-- etc.
+-   Create a column of domain type
+-   Read/write values from/to domain column
+-   Use it as index if base type can be used as index
+-   Call functions with values of domain column
+-   etc.
 
 ### Extra Features of Domains {#extra-features-of-domains}
 
-- Explicit column type name in `SHOW CREATE TABLE` or `DESCRIBE TABLE`
-- Input from human-friendly format with `INSERT INTO domain_table(domain_column) VALUES(...)`
-- Output to human-friendly format for `SELECT domain_column FROM domain_table`
-- Loading data from external source in human-friendly format: `INSERT INTO domain_table FORMAT CSV ...`
+-   Explicit column type name in `SHOW CREATE TABLE` or `DESCRIBE TABLE`
+-   Input from human-friendly format with `INSERT INTO domain_table(domain_column) VALUES(...)`
+-   Output to human-friendly format for `SELECT domain_column FROM domain_table`
+-   Loading data from external source in human-friendly format: `INSERT INTO domain_table FORMAT CSV ...`
 
 ### Limitations {#limitations}
 
-- Can’t convert index column of base type to domain type via `ALTER TABLE`.
-- Can’t implicitly convert string values into domain values when inserting data from another column or table.
-- Domain adds no constrains on stored values.
+-   Can’t convert index column of base type to domain type via `ALTER TABLE`.
+-   Can’t implicitly convert string values into domain values when inserting data from another column or table.
+-   Domain adds no constrains on stored values.
 
 [Original article](https://clickhouse.tech/docs/en/data_types/domains/overview) <!--hide-->
diff --git a/docs/en/data_types/enum.md b/docs/en/data_types/enum.md
@@ -6,8 +6,8 @@ Named values must be declared as `'string' = integer` pairs. ClickHouse stores o
 
 ClickHouse supports:
 
-- 8-bit `Enum`. It can contain up to 256 values enumerated in the `[-128, 127]` range.
-- 16-bit `Enum`. It can contain up to 65536 values enumerated in the `[-32768, 32767]` range.
+-   8-bit `Enum`. It can contain up to 256 values enumerated in the `[-128, 127]` range.
+-   16-bit `Enum`. It can contain up to 65536 values enumerated in the `[-32768, 32767]` range.
 
 ClickHouse automatically chooses the type of `Enum` when data is inserted. You can also use `Enum8` or `Enum16` types to be sure in the size of storage.
 

diff --git a/docs/en/data_types/fixedstring.md b/docs/en/data_types/fixedstring.md
@@ -14,17 +14,17 @@ The `FixedString` type is efficient when data has the length of precisely `N` by
 
 Examples of the values that can be efficiently stored in `FixedString`-typed columns:
 
-- The binary representation of IP addresses (`FixedString(16)` for IPv6).
-- Language codes (ru\_RU, en\_US … ).
-- Currency codes (USD, RUB … ).
-- Binary representation of hashes (`FixedString(16)` for MD5, `FixedString(32)` for SHA256).
+-   The binary representation of IP addresses (`FixedString(16)` for IPv6).
+-   Language codes (ru\_RU, en\_US … ).
+-   Currency codes (USD, RUB … ).
+-   Binary representation of hashes (`FixedString(16)` for MD5, `FixedString(32)` for SHA256).
 
 To store UUID values, use the [UUID](uuid.md) data type.
 
 When inserting the data, ClickHouse:
 
-- Complements a string with null bytes if the string contains fewer than `N` bytes.
-- Throws the `Too large value for FixedString(N)` exception if the string contains more than `N` bytes.
+-   Complements a string with null bytes if the string contains fewer than `N` bytes.
+-   Throws the `Too large value for FixedString(N)` exception if the string contains more than `N` bytes.
 
 When selecting the data, ClickHouse does not remove the null bytes at the end of the string. If you use the `WHERE` clause, you should add null bytes manually to match the `FixedString` value. The following example illustrates how to use the `WHERE` clause with `FixedString`.