[docs] fix/update many legacy external links (#18282)

Author: blinkov

ydb/apps/ydb/CHANGELOG.md

@@ -293,7 +293,7 @@ Also now you can load test YDB topics, using wide transactions that span over al
 * You can now save the IAM service URL in a profile.
 * Added support for username and password-based authentication without specifying the password.
 * Added support for AWS profiles in the [ydb export s3](reference/ydb-cli/export-import/auth-s3.md#auth) command.
-* You can now create profiles using `stdin`. For example, you can pass the [YC CLI](https://cloud.yandex.ru/docs/cli/) `yc ydb database get information` command output to the `ydb config profile create` command input.
+* You can now create profiles using `stdin`. For example, you can pass the [YC CLI](https://yandex.cloud/docs/cli/) `yc ydb database get information` command output to the `ydb config profile create` command input.
 
 ### Bug fixes
 

ydb/docs/en/core/_includes/parameterized-query.md

@@ -3,9 +3,9 @@ A brief help is provided below. For a detailed description with examples, see [{
 | Name | Description |
 ---|---
 | `-p, --param` | The value of a single parameter of a YQL query, in the format: `$name=value`, where `$name` is the parameter name and `value` is its value (a valid [JSON value](https://www.json.org/json-ru.html)). |
-| `--param-file` | Name of the file in [JSON]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/JSON){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/JSON){% endif %} format and in [UTF-8]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/UTF-8){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/UTF-8){% endif %} encoding that specifies values of the parameters matched against the YQL query parameters by key names. |
-| `--input-format` | Format of parameter values. Applies to all the methods of parameter transmission (among command parameters, in a file or using `stdin`).<br/>Acceptable values:<ul><li>`json-unicode` (default):[JSON]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/JSON){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/JSON){% endif %}.</li><li>`json-base64`: [JSON]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/JSON){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/JSON){% endif %} format in which values of binary string parameters (`DECLARE $par AS String`) are [Base64]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/Base64){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/Base64){% endif %}-encoded.</li></ul> |
-| `--stdin-format` | The parameter format and framing for `stdin`. To set both values, specify the parameter twice.<br/>**Format of parameter encoding for `stdin`**<br/>Acceptable values:<ul><li>`json-unicode`: [JSON]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/JSON){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/JSON){% endif %}.</li><li>`json-base64`: [JSON]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/JSON){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/JSON){% endif %} format in which values of binary string parameters (`DECLARE $par AS String`) are [Base64]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/Base64){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/Base64){% endif %}-encoded.</li><li>`raw` is binary data; the parameter name is set in `--stdin-par`.</li></ul>If the format of parameter encoding for `stdin` isn't specified, the format set in `--input-format` is used.<br/><br/>**Classification of parameter sets for `stdin` (framing)**<br/>Acceptable values:<ul><li>`no-framing` (default): Framing isn't used</li><li>`newline-delimited`: The newline character is used in `stdin` to end a given parameter set, separating it from the next one.</li></ul> |
+| `--param-file` | Name of the file in [JSON](https://en.wikipedia.org/wiki/JSON) format and in [UTF-8](https://en.wikipedia.org/wiki/UTF-8) encoding that specifies values of the parameters matched against the YQL query parameters by key names. |
+| `--input-format` | Format of parameter values. Applies to all the methods of parameter transmission (among command parameters, in a file or using `stdin`).<br/>Acceptable values:<ul><li>`json-unicode` (default):[JSON](https://en.wikipedia.org/wiki/JSON).</li><li>`json-base64`: [JSON](https://en.wikipedia.org/wiki/JSON) format in which values of binary string parameters (`DECLARE $par AS String`) are [Base64](https://en.wikipedia.org/wiki/Base64)-encoded.</li></ul> |
+| `--stdin-format` | The parameter format and framing for `stdin`. To set both values, specify the parameter twice.<br/>**Format of parameter encoding for `stdin`**<br/>Acceptable values:<ul><li>`json-unicode`: [JSON](https://en.wikipedia.org/wiki/JSON).</li><li>`json-base64`: [JSON](https://en.wikipedia.org/wiki/JSON) format in which values of binary string parameters (`DECLARE $par AS String`) are [Base64](https://en.wikipedia.org/wiki/Base64)-encoded.</li><li>`raw` is binary data; the parameter name is set in `--stdin-par`.</li></ul>If the format of parameter encoding for `stdin` isn't specified, the format set in `--input-format` is used.<br/><br/>**Classification of parameter sets for `stdin` (framing)**<br/>Acceptable values:<ul><li>`no-framing` (default): Framing isn't used</li><li>`newline-delimited`: The newline character is used in `stdin` to end a given parameter set, separating it from the next one.</li></ul> |
 | `--stdin-par` | The name of the parameter whose value will be sent over `stdin` is specified without a `$`. |
 | `--batch` | The batch mode of transmitting parameter sets received via `stdin`.<br/>Acceptable values:<ul><li>`iterative` (default): Batch mode is disabled</li><li>`full`: Full-scale batch mode is enabled</li><li>`adaptive`: Adaptive batching is enabled |
 | `--batch-limit` | A maximum number of sets of parameters per batch in the adaptive batch mode. The setting of `0` removes the limit.<br/><br/>The default value is `1000`.<br/><br/> |

ydb/docs/en/core/changelog-cli.md

@@ -320,7 +320,7 @@ Release date: November 18, 2022. To update to version **2.1.0**, select the [Dow
 * You can now save the IAM service URL in a profile.
 * Added support for username and password-based authentication without specifying the password.
 * Added support for AWS profiles in the [ydb export s3](reference/ydb-cli/export-import/auth-s3.md#auth) command.
-* You can now create profiles using `stdin`. For example, you can pass the [YC CLI](https://cloud.yandex.ru/docs/cli/) `yc ydb database get information` command output to the `{{ ydb-cli }} config profile create` command input.
+* You can now create profiles using `stdin`. For example, you can pass the [YC CLI](https://yandex.cloud/docs/cli/) `yc ydb database get information` command output to the `{{ ydb-cli }} config profile create` command input.
 
 ### Bug fixes
 

ydb/docs/en/core/concepts/federated_query/s3/_includes/date_formats.md

@@ -1,7 +1,7 @@
 |Name|Description|Example|
 |---|---|---|
 |`POSIX`|String in `%Y-%m-%d %H:%M:%S` format|2001-03-26 16:10:00|
-|`ISO`|Format, corresponding to the [ISO 8601](https://ru.wikipedia.org/wiki/ISO_8601) standard|2001-03-26 16:10:00Z|
+|`ISO`|Format, corresponding to the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) standard|2001-03-26 16:10:00Z|
 |`UNIX_TIME_SECONDS`|Number of seconds that have elapsed since the 1st of january 1970 (00:00:00 UTC)|985623000|
 |`UNIX_TIME_MILLISECONDS`|Number of milliseconds that have elapsed since the 1st of january 1970 (00:00:00 UTC)|985623000000|
 |`UNIX_TIME_MICROSECONDS`|Number of microseconds that have elapsed since the 1st of january 1970 (00:00:00 UTC)|985623000000000|

ydb/docs/en/core/devops/ansible/initial-deployment.md

@@ -138,7 +138,7 @@ The values of the `system_timezone` and `system_ntp_servers` variables depend on
 - Yandex Cloud
 
   * `system_timezone`: Europe/Moscow
-  * `system_ntp_servers`: [0.ru.pool.ntp.org, 1.ru.pool.ntp.org, ntp0.NL.net, ntp2.vniiftri.ru, ntp.ix.ru, ntps1-1.cs.tu-berlin.de] [Learn more](https://cloud.yandex.ru/en/docs/tutorials/infrastructure-management/ntp) about Yandex Cloud NTP server settings.
+  * `system_ntp_servers`: [0.ru.pool.ntp.org, 1.ru.pool.ntp.org, ntp0.NL.net, ntp2.vniiftri.ru, ntp.ix.ru, ntps1-1.cs.tu-berlin.de] [Learn more](https://yandex.cloud/en/docs/tutorials/infrastructure-management/ntp) about Yandex Cloud NTP server settings.
 
 {% endlist %}
 

ydb/docs/en/core/devops/kubernetes/initial-deployment.md

@@ -1,6 +1,6 @@
 # Getting started with {{ ydb-short-name }} in {{ k8s }}
 
-Deploying {{ ydb-short-name }} in {{ k8s }} is a simple way to set up and run a {{ ydb-short-name }} cluster. {{ k8s }} allows to use an universal approach to managing your application in any cloud service provider. This guide provides instructions on how to deploy {{ ydb-short-name }} in [AWS EKS](https://aws.amazon.com/eks/) or [{{ managed-k8s-full-name }}](https://cloud.yandex.com/services/managed-kubernetes).
+Deploying {{ ydb-short-name }} in {{ k8s }} is a simple way to set up and run a {{ ydb-short-name }} cluster. {{ k8s }} allows to use an universal approach to managing your application in any cloud service provider. This guide provides instructions on how to deploy {{ ydb-short-name }} in [AWS EKS](https://aws.amazon.com/eks/) or [{{ managed-k8s-full-name }}](https://yandex.cloud/services/managed-kubernetes).
 
 ## Prerequisites
 
@@ -43,7 +43,7 @@ Skip this section if you have already configured a suitable {{ k8s }} cluster.
 
 - {{ managed-k8s-full-name }}
 
-  Follow the instructions in the [{{ managed-k8s-full-name }} quick start guide](https://cloud.yandex.com/en/docs/managed-kubernetes/quickstart).
+  Follow the instructions in the [{{ managed-k8s-full-name }} quick start guide](https://yandex.cloud/en/docs/managed-kubernetes/quickstart).
 
 {% endlist %}
 

ydb/docs/en/core/integrations/ingestion/import-jdbc.md

@@ -178,7 +178,7 @@ Below is the explanation of the configuration file structure:
          In case the Service Account authentication is used, either explicitly
          or through the YDB_SERVICE_ACCOUNT_KEY_FILE_CREDENTIALS env, the key file
          must be generated as written in the following document:
-            https://cloud.yandex.com/en/docs/iam/operations/authorized-key/create
+            https://yandex.cloud/en/docs/iam/operations/authorized-key/create
         -->
         <!-- Custom TLS certificates, if needed -->
         <tls-certificate-file>ca.crt</tls-certificate-file>

ydb/docs/en/core/reference/ydb-cli/_includes/result_format_csv_tsv.md

@@ -1,2 +1,2 @@
-* `csv`: Output in [CSV](https://ru.wikipedia.org/wiki/CSV) format.
-* `tsv`: Output in [TSV](https://ru.wikipedia.org/wiki/TSV) format.
+* `csv`: Output in [CSV](https://en.wikipedia.org/wiki/CSV) format.
+* `tsv`: Output in [TSV](https://en.wikipedia.org/wiki/Tab-separated_values) format.

ydb/docs/en/core/reference/ydb-cli/export-import/_includes/import-file.md

@@ -56,7 +56,7 @@ The file includes data without any additional information. The `,` character is
 
 {% note info %}
 
-The `release_date` column in the `series` table has the [Date](../../../../yql/reference/types/primitive.md#datetime) type, so the release date in the imported file has a numeric format. To import values in the [timestamp]{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/ISO_8601){% endif %}{% if lang == "en" %}(https://en.wikipedia.org/wiki/ISO_8601){% endif %} format, use string-type table columns for them. Alternatively, you can import them to a temporary table and convert them to a relevant type.
+The `release_date` column in the `series` table has the [Date](../../../../yql/reference/types/primitive.md#datetime) type, so the release date in the imported file has a numeric format. To import values in the [timestamp](https://en.wikipedia.org/wiki/ISO_8601) format, use string-type table columns for them. Alternatively, you can import them to a temporary table and convert them to a relevant type.
 
 {% endnote %}
 

ydb/docs/en/core/reference/ydb-cli/export-import/_includes/s3_conn.md

@@ -47,9 +47,9 @@ If a certain authentication parameter is omitted in the command line and cannot
 
 ### {{ yandex-cloud }}
 
-Below is an example of getting access keys for the [{{ yandex-cloud }} Object Storage]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/storage/){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/storage/){% endif %} using the {{ yandex-cloud }} CLI.
+Below is an example of getting access keys for the [{{ yandex-cloud }} Object Storage](https://yandex.cloud/docs/storage/) using the {{ yandex-cloud }} CLI.
 
-1. [Install and set up]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/cli/quickstart){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/cli/quickstart){% endif %} the {{ yandex-cloud }} CLI.
+1. [Install and set up](https://yandex.cloud/docs/cli/quickstart) the {{ yandex-cloud }} CLI.
 
 2. Use the following command to get the ID of your cloud folder (`folder-id`) (you'll need to add it to the commands below):
 
@@ -63,7 +63,7 @@ Below is an example of getting access keys for the [{{ yandex-cloud }} Object St
    folder-id: b2ge70qdcff4bo9q6t19
    ```
 
-3. To [create a service account]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/iam/operations/sa/create){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/iam/operations/sa/create){% endif %}, run the command:
+3. To [create a service account](https://yandex.cloud/docs/iam/operations/sa/create), run the command:
 
    ```bash
    yc iam service-account create --name s3account
@@ -79,7 +79,7 @@ Below is an example of getting access keys for the [{{ yandex-cloud }} Object St
    yc iam service-account get --name <account-name>
    ```
 
-4. [Grant roles to your service account]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/iam/operations/sa/assign-role-for-sa){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/iam/operations/sa/assign-role-for-sa){% endif %} according to your intended S3 access level by running the command:
+4. [Grant roles to your service account](https://yandex.cloud/docs/iam/operations/sa/assign-role-for-sa) according to your intended S3 access level by running the command:
 
    {% list tabs %}
 
@@ -101,9 +101,9 @@ Below is an example of getting access keys for the [{{ yandex-cloud }} Object St
 
    Where `<folder-id>` is the cloud folder ID that you retrieved at step 2 and `<s3-account-id>` is the id of the account you created at step 3.
 
-   You can also read a [full list]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/iam/concepts/access-control/roles#object-storage){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/iam/concepts/access-control/roles#object-storage){% endif %} of {{ yandex-cloud }} roles.
+   You can also read a [full list](https://yandex.cloud/docs/iam/concepts/access-control/roles#object-storage) of {{ yandex-cloud }} roles.
 
-5. Get [static access keys]{% if lang == "ru" %}(https://cloud.yandex.ru/docs/iam/operations/sa/create-access-key){% endif %}{% if lang == "en" %}(https://cloud.yandex.com/docs/iam/operations/sa/create-access-key){% endif %} by running the command:
+5. Get [static access keys](https://yandex.cloud/docs/iam/operations/sa/create-access-key) by running the command:
 
    ```bash
    yc iam access-key create --service-account-name s3account