Исправить ссылки и термины в EN

fixed

ref:0d3ade58ed840253e293a982ba0b507d0bee03de

13 files changed, 18 insertions, 18 deletions

diff --git a/ydb/docs/en/core/best_practices/_includes/timeouts.md b/ydb/docs/en/core/best_practices/_includes/timeouts.md
index 28754f481b..5d260a3a6d 100644
--- a/ydb/docs/en/core/best_practices/_includes/timeouts.md
+++ b/ydb/docs/en/core/best_practices/_includes/timeouts.md
@@ -1,5 +1,5 @@
 ---
-title: Using timeouts in Yandex Database (YDB)
+title: Using timeouts in YDB
 description: 'The operation_timeout value determines the time during which the query result is interesting to the user. If the operation has not been performed during this time, the server returns an error with the Timeout code and tries to terminate the execution of the request, but the cancellation of the request is not guaranteed. It is always recommended to set both the operation timeout and the transport timeout.'
 ---
 This section describes available timeouts and provides examples of their usage in various programming languages.
diff --git a/ydb/docs/en/core/concepts/_includes/databases/intro.md b/ydb/docs/en/core/concepts/_includes/databases/intro.md
index f833273d05..fd685bdeff 100644
--- a/ydb/docs/en/core/concepts/_includes/databases/intro.md
+++ b/ydb/docs/en/core/concepts/_includes/databases/intro.md
@@ -1,6 +1,6 @@
 ---
-title: "Terms and definitions {{ ydb-full-name }}"
-description: "A database (DB) {{ ydb-full-name }}: is an isolated, consistent set of data that is accessed through the {{ ydb-full-name }}, service, which provides scalability, fault tolerance, and automatic data replication."
+title: "Terms and definitions YDB"
+description: "A database (DB) YDB: is an isolated, consistent set of data that is accessed through the YDB, service, which provides scalability, fault tolerance, and automatic data replication."
 ---
 # Terms and definitions
 
diff --git a/ydb/docs/en/core/concepts/_includes/datamodel/table.md b/ydb/docs/en/core/concepts/_includes/datamodel/table.md
index 0e0fdf619c..5939748692 100644
--- a/ydb/docs/en/core/concepts/_includes/datamodel/table.md
+++ b/ydb/docs/en/core/concepts/_includes/datamodel/table.md
@@ -8,7 +8,7 @@ A table in {{ ydb-short-name }} is a [relational table](https://en.wikipedia.org
 
 Figure 1 shows the schema of a ```Series``` table with four columns, named ```SeriesId```, ```ReleaseDate```, ```SeriesInfo```, and ```Title```, with the ```Uint64?``` data type for the first two columns and ```String?``` for the others. The ```SeriesId``` column is declared the primary key.
 
-{{ ydb-short-name }} uses [YQL]{% if audience != "external" %}(https://yql.yandex-team.ru/docs/ydb/types/){% else %}(../../datatypes.md){% endif %} data types. {% if audience != "external" %} [Simple YQL data types](https://yql.yandex-team.ru/docs/ydb/types/primitive/) {% else %} [Simple YQL data types](../../../yql/reference/types/primitive.md) {% endif %} can be used as column types. All columns may contain a special NULL value to indicate a missing value.
+{{ ydb-short-name }} uses [YQL](../../datatypes.md) data types. [Simple YQL data types](../../../yql/reference/types/primitive.md) can be used as column types. All columns may contain a special NULL value to indicate a missing value.
 
 {{ ydb-short-name }} tables always have one or more columns that make up the key ([primary key](https://en.wikipedia.org/wiki/Unique_key)). Each table row has a unique key value, so there can be no more than one row per key value. {{ ydb-short-name }} tables are always ordered by key. This means that you can efficiently make point reads by key and range-based queries by key or key prefix (actually using an index). In the example above, the key columns are highlighted in gray and marked with a special sign. Tables consisting only of key columns are supported. However, you can't create tables without a primary key.
 
diff --git a/ydb/docs/en/core/concepts/_includes/index/intro.md b/ydb/docs/en/core/concepts/_includes/index/intro.md
index bca0c2eb47..c0781dae75 100644
--- a/ydb/docs/en/core/concepts/_includes/index/intro.md
+++ b/ydb/docs/en/core/concepts/_includes/index/intro.md
@@ -1,6 +1,6 @@
 ---
-title: Yandex Database (YDB). DBMS overview
-description: "Yandex Database (YDB): is a horizontally scalable distributed fault-tolerant DBMS. YDB is designed to meet high performance requirements. For example, a typical server can handle dozens of thousands of queries per second. The system is designed to handle hundreds of petabytes of data."
+title: YDB. DBMS overview
+description: "YDB: is a horizontally scalable distributed fault-tolerant DBMS. YDB is designed to meet high performance requirements. For example, a typical server can handle dozens of thousands of queries per second. The system is designed to handle hundreds of petabytes of data."
 ---
 # {{ ydb-short-name }} overview
 
diff --git a/ydb/docs/en/core/concepts/_includes/serverless_and_dedicated/01_intro.md b/ydb/docs/en/core/concepts/_includes/serverless_and_dedicated/01_intro.md
index 540c543c9e..a6e18f090e 100644
--- a/ydb/docs/en/core/concepts/_includes/serverless_and_dedicated/01_intro.md
+++ b/ydb/docs/en/core/concepts/_includes/serverless_and_dedicated/01_intro.md
@@ -1,5 +1,5 @@
 ---
-title: Serverless and Dedicated modes in Yandex Database
+title: Serverless and Dedicated modes in YDB
 description: "YDB databases can be created in two modes Dedicated and Serverless. Dedicated mode of operation assumes that resources for Tablet instances and for executing YQL queries are selected from resources explicitly allocated for the compute database. In the Serverless mode of operation, the YDB infrastructure determines how many computing resources need to be allocated to service the user base."
 keywords:
   - ydb
diff --git a/ydb/docs/en/core/deploy/production_checklist.md b/ydb/docs/en/core/deploy/production_checklist.md
index a8ccfef6eb..6f3295f58f 100644
--- a/ydb/docs/en/core/deploy/production_checklist.md
+++ b/ydb/docs/en/core/deploy/production_checklist.md
@@ -1,6 +1,6 @@
 ## Checklist for deploying your product environment
 
-This section provides recommendations for deploying {{ ydb-full-name }} in product environments.
+This section provides recommendations for deploying YDB in product environments.
 
 ## Topology
 
diff --git a/ydb/docs/en/core/faq/_includes/common.md b/ydb/docs/en/core/faq/_includes/common.md
index d63dfbc107..7d656a61f4 100644
--- a/ydb/docs/en/core/faq/_includes/common.md
+++ b/ydb/docs/en/core/faq/_includes/common.md
@@ -1,6 +1,6 @@
 ---
-title: "Yandex Database. FAQ"
-description: "What is Yandex Database? For what tasks is it worth using Yandex Database, and for which virtual machines with databases? What part of the management and maintenance of databases does Yandex Database take on? Answers to these and other questions in this article."
+title: "YDB. FAQ"
+description: "What is YDB? For what tasks is it worth using YDB, and for which virtual machines with databases? What part of the management and maintenance of databases does YDB take on? Answers to these and other questions in this article."
 ---
 # General questions about {{ ydb-short-name }}
 
diff --git a/ydb/docs/en/core/maintenance/_includes/backup_and_recovery/01_intro.md b/ydb/docs/en/core/maintenance/_includes/backup_and_recovery/01_intro.md
index 4aae62c250..3c1d97d71a 100644
--- a/ydb/docs/en/core/maintenance/_includes/backup_and_recovery/01_intro.md
+++ b/ydb/docs/en/core/maintenance/_includes/backup_and_recovery/01_intro.md
@@ -1,5 +1,5 @@
 ---
-title: "Yandex Database (YDB) backups"
+title: "YDB backups"
 description: "This section describes supported methods for creating YDB database backups and restoring data from previously created backups. YDB lets you use the following destinations to create backups: CSV files on the file system and AWS S3-compatible storage."
 ---
 # Backups
diff --git a/ydb/docs/en/core/reference/ydb-sdk/example/go/index.md b/ydb/docs/en/core/reference/ydb-sdk/example/go/index.md
index 8e20c29b52..0c4ed38f41 100644
--- a/ydb/docs/en/core/reference/ydb-sdk/example/go/index.md
+++ b/ydb/docs/en/core/reference/ydb-sdk/example/go/index.md
@@ -18,7 +18,7 @@ Next, from the same working directory, run the command to start the test app. Th
 
 {% include [init.md](../_includes/steps/01_init.md) %}
 
-To work with `YDB` in `Go`, import the `ydb-go-sdk` driver package:
+To work with YDB in `Go`, import the `ydb-go-sdk` driver package:
 
 ```go
 import (
@@ -65,7 +65,7 @@ defer func() {
 }
 ```
 
-The `db` object is an input point for working with `YDB` services.
+The `db` object is an input point for working with YDB services.
 To work with the table service, use the `db.Table()` client.
 The client of the table service provides an `API` for making queries to tables.
 The most popular method is `db.Table().Do(ctx, op)`. It implements background session creation and repeated attempts to perform the `op` user operation where the created session is passed to the user-defined code.
diff --git a/ydb/docs/en/core/reference/ydb-sdk/recipes/_includes/session_pool_limit.md b/ydb/docs/en/core/reference/ydb-sdk/recipes/_includes/session_pool_limit.md
index cb4507ed54..5fd4fd8b85 100644
--- a/ydb/docs/en/core/reference/ydb-sdk/recipes/_includes/session_pool_limit.md
+++ b/ydb/docs/en/core/reference/ydb-sdk/recipes/_includes/session_pool_limit.md
@@ -5,8 +5,8 @@
 The client's session pool size affects resource consumption (RAM, CPU) on the server side of YDB.
 Simple math: if `1000` clients of the same DB have `1000` sessions each, `100000` actors (workers, session performers) are created on the server side. If you don't limit the number of sessions on the client, this may result in a slow cluster that is close to a failure.
 By default, the `YDB SDK` limits the number of sessions to `50`.
-A good recommendation is to set the limit on the number of client sessions to the minimum required for the normal operation of the client app. Keep in mind that sessions are single-threaded  both on the server and client side. So if the application needs to make `1000` simultaneous (`inflight`) requests to `YDB` for its estimated load, the limit should be set to `1000` sessions.
-Here it's necessary to distinguish between the estimated `RPS` (requests per second) and `inflight`. In the first case, this is the total number of requests to `YDB` completed within `1` second. For example, if `RPS`=`10000` and the average `latency` is `100`ms, it's sufficient to set the session limit to `1000`. This means that each session will perform an average of `10` consecutive requests  for the estimated second.
+A good recommendation is to set the limit on the number of client sessions to the minimum required for the normal operation of the client app. Keep in mind that sessions are single-threaded  both on the server and client side. So if the application needs to make `1000` simultaneous (`inflight`) requests to YDB for its estimated load, the limit should be set to `1000` sessions.
+Here it's necessary to distinguish between the estimated `RPS` (requests per second) and `inflight`. In the first case, this is the total number of requests to YDB completed within `1` second. For example, if `RPS`=`10000` and the average `latency` is `100`ms, it's sufficient to set the session limit to `1000`. This means that each session will perform an average of `10` consecutive requests  for the estimated second.
 
 Below are examples of the code for setting the session pool limit in different `YDB SDKs`.
 
diff --git a/ydb/docs/en/overlay/toc_p.yaml b/ydb/docs/en/overlay/toc_p.yaml
index 762b9b82ac..b3bc4402e0 100644
--- a/ydb/docs/en/overlay/toc_p.yaml
+++ b/ydb/docs/en/overlay/toc_p.yaml
@@ -1,4 +1,4 @@
-title: Yandex Database
+title: YDB
 href: index.yaml
 items:
 - include: { mode: link, path: toc_i.yaml }
\ No newline at end of file
diff --git a/ydb/docs/ru/core/concepts/_includes/datamodel/table.md b/ydb/docs/ru/core/concepts/_includes/datamodel/table.md
index f9d38de5b7..affd298716 100644
--- a/ydb/docs/ru/core/concepts/_includes/datamodel/table.md
+++ b/ydb/docs/ru/core/concepts/_includes/datamodel/table.md
@@ -7,7 +7,7 @@
 
 На рисунке 1 приведена схема таблицы ```Series``` из четырех столбцов c именами ```SeriesId```, ```ReleaseDate```, ```SeriesInfo``` и ```Title``` и типами данных ```Uint64?``` для первых двух и ```String?``` для последних. Первичным ключом объявлен столбец ```SeriesId```.
 
-{{ ydb-short-name }} использует типы данных [YQL]{% if audience != "external" %}(https://yql.yandex-team.ru/docs/ydb/types/){% else %}[](../../datatypes.md){% endif %}, в качестве типов столбцов могут использоваться {% if audience != "external" %} [простые типы данных YQL](https://yql.yandex-team.ru/docs/ydb/types/primitive/) {% else %} [простые типы данных YQL](../../../yql/reference/types/primitive.md) {% endif %} . Все столбцы могут содержать специальное значение NULL, используемое для обозначения отсутствия значения.
+{{ ydb-short-name }} использует типы данных [YQL](../../datatypes.md), в качестве типов столбцов могут использоваться [простые типы данных YQL](../../../yql/reference/types/primitive.md). Все столбцы могут содержать специальное значение NULL, используемое для обозначения отсутствия значения.
 
 Таблица {{ ydb-short-name }} всегда имеет один или несколько столбцов, составляющих ключ ([primary key](https://en.wikipedia.org/wiki/Unique_key)). Строки таблицы уникальны по ключу, то есть для одного значения ключа может быть не больше одной строки. Таблица {{ ydb-short-name }} всегда упорядочена по ключу. Это означает, что точечное чтение по ключу, а также диапазонные запросы по ключу или префиксу ключа выполняются эффективно (фактически используя индекс). В примере выше ключевые столбцы выделены серым цветом и отмечены специальным знаком. Допускаются таблицы, состоящие только из ключевых столбцов. Таблицы без первичного ключа создавать нельзя.
 
diff --git a/ydb/docs/ru/core/deploy/production_checklist.md b/ydb/docs/ru/core/deploy/production_checklist.md
index 9e4b8a4929..c1669511b8 100644
--- a/ydb/docs/ru/core/deploy/production_checklist.md
+++ b/ydb/docs/ru/core/deploy/production_checklist.md
@@ -1,5 +1,5 @@
 ## Чек-лист для развертывания продуктового окружения
-В данном разделе проводятся рекомендации для развертывания {{ ydb-full-name }} в продуктовых окружениях.
+В данном разделе проводятся рекомендации для развертывания {{ ydb-short-name }} в продуктовых окружениях.
 
 ## Топология
 При планировании развертывания важно правильно выбрать топологию кластера, исходя из необходимой отказоустойчивости: