New translations quick-start.mdx (Russian)

Author: benface

website/src/pages/ru/subgraphs/quick-start.mdx

@@ -7,19 +7,19 @@ Learn how to easily build, publish and query a [Subgraph](/subgraphs/developing/
 ## Предварительные требования
 
 - Криптовалютный кошелек
-- A smart contract address on a [supported network](/supported-networks/)
-- [Node.js](https://nodejs.org/) installed
-- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+- Адрес смарт-контракта в [поддерживаемой сети](/supported-networks/)
+- [Node.js](https://nodejs.org/) установлен
+- Менеджер пакетов на Ваш выбор (`npm`, `yarn` или `pnpm`)
 
-## How to Build a Subgraph
+## Как создать субграф
 
 ### 1. Create a Subgraph in Subgraph Studio
 
 Перейдите в [Subgraph Studio](https://thegraph.com/studio/) и подключите свой кошелек.
 
 Subgraph Studio lets you create, manage, deploy, and publish Subgraphs, as well as create and manage API keys.
 
-Click "Create a Subgraph". It is recommended to name the Subgraph in Title Case: "Subgraph Name Chain Name".
+Нажмите "Создать субграф". Рекомендуется называть субграф с использованием Заглавного регистра: "Subgraph Name Chain Name".
 
 ### 2. Установка Graph CLI
 
@@ -49,24 +49,24 @@ The following command initializes your Subgraph from an existing contract:
 graph init
 ```
 
-If your contract is verified on the respective blockscanner where it is deployed (such as [Etherscan](https://etherscan.io/)), then the ABI will automatically be created in the CLI.
+Если Ваш контракт верифицирован на соответствующем блоксканере, где он развернут (например, [Etherscan](https://etherscan.io/)), то ABI будет автоматически создан в CLI.
 
 When you initialize your Subgraph, the CLI will ask you for the following information:
 
 - **Protocol**: Choose the protocol your Subgraph will be indexing data from.
 - **Subgraph slug**: Create a name for your Subgraph. Your Subgraph slug is an identifier for your Subgraph.
 - **Directory**: Choose a directory to create your Subgraph in.
 - **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from.
-- **Contract address**: Locate the smart contract address you’d like to query data from.
-- **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file.
+- **Адрес контракта**: Найдите адрес смарт-контракта, из которого Вы хотите запрашивать данные.
+- **ABI**: Если ABI не заполнен автоматически, Вам придется ввести его вручную в формате JSON.
 - **Start Block**: You should input the start block to optimize Subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed.
-- **Contract Name**: Input the name of your contract.
+- **Имя контракта**: Введите имя Вашего контракта.
 - **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event.
-- **Add another contract** (optional): You can add another contract.
+- **Добавление еще одного контракта (опционально)**: Вы можете добавить еще один контракт.
 
 See the following screenshot for an example for what to expect when initializing your Subgraph:
 
-![Subgraph command](/img/CLI-Example.png)
+![Команда субграфа](/img/CLI-Example.png)
 
 ### 4. Edit your Subgraph
 
@@ -82,7 +82,7 @@ For a detailed breakdown on how to write your Subgraph, check out [Creating a Su
 
 ### 5. Deploy your Subgraph
 
-> Remember, deploying is not the same as publishing.
+> Помните, развертывание — это не то же самое, что публикация.
 
 When you **deploy** a Subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it. A deployed Subgraph's indexing is performed by the [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/), which is a single Indexer owned and operated by Edge & Node, rather than by the many decentralized Indexers in The Graph Network. A **deployed** Subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes.
 
@@ -107,7 +107,7 @@ graph deploy <SUBGRAPH_SLUG>
 ```
 ````
 
-The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
+CLI запросит метку версии. Настоятельно рекомендуется использовать [семантическую версию](https://semver.org/), например, `0.0.1`.
 
 ### 6. Review your Subgraph
 
@@ -150,20 +150,20 @@ As of version 0.73.0, you can also publish your Subgraph with the Graph CLI.
 graph codegen && graph build
 ```
 
-Then,
+Затем,
 
 ```sh
 graph publish
 ```
 ````
 
-3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice.
+3. Откроется окно, где Вы сможете подключить свой кошелек, добавить метаданные и развернуть финализированный субграф в выбранной Вами сети.
 
 ![cli-ui](/img/cli-ui.png)
 
-To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/).
+Чтобы настроить ваше развертывание, смотрите раздел [Публикация субграфа](/subgraphs/developing/publishing/publishing-a-subgraph/).
 
-#### Adding signal to your Subgraph
+#### Добавление сигнала к Вашему субграфу
 
 1. To attract Indexers to query your Subgraph, you should add GRT curation signal to it.
 
@@ -173,11 +173,11 @@ To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/
 
    - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on Subgraph feature usage and supported networks.
 
-To learn more about curation, read [Curating](/resources/roles/curating/).
+Чтобы узнать больше о кураторстве, прочитайте статью [Курирование](/resources/roles/curating/).
 
 To save on gas costs, you can curate your Subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/studio-publish-modal.png)
+![Публикация субграфа](/img/studio-publish-modal.png)
 
 ### 8. Query your Subgraph