Update ydb/docs/en/core/reference/ydb-sdk/health-check-api.md

Co-authored-by: Ivan Blinkov <ivan@blinkov.ru>

ydb/docs/en/core/reference/ydb-sdk/health-check-api.md

@@ -109,25 +109,25 @@ struct TSelfCheckSettings : public TOperationRequestSettings<TSelfCheckSettings>
 | `Group failed` | A storage group lost its integrity. |
 ||`HealthCheck` checks various parameters (fault tolerance mode, number of failed disks, disk status, etc.) and, depending on this, sets the appropriate status and displays a message. |
 | **VDISK** ||
-| `System tablet BSC didn't provide known status` | This case is not expected, it inner proble. |
-| `VDisk is not available` | the disk is not operational at all. |
-| `VDisk is being initialized` | initialization in process. |
-| `Replication in progress` | the disk accepts queries, but not all the data was replicated. |
-| `VDisk have space issue` | These issues depend solely on the underlying `PDISK` layer. |
+| `System tablet BSC didn't provide known status` | This case is not expected; it is an internal problem. |
+| `VDisk is not available` | The disk is not operational at all. |
+| `VDisk is being initialized` | The disk initialization is in progress. |
+| `Replication in progress` | The disk accepts queries, but not all the data has yet been replicated. |
+| `VDisk has space issues` | These issues depend solely on the underlying `PDISK` layer. |
 | **PDISK** ||
-| `Unknown PDisk state` | `HealthCheck` the system can't parse pdisk state. |
-| `PDisk is inactive/PDisk state is FAULTY/BROKEN/TO_BE_REMOVED` | Indicates problems with a physical disk. |
+| `Unknown PDisk state` | `HealthCheck` cannot parse the PDisk state. |
+| `PDisk is inactive/PDisk state is FAULTY/BROKEN/TO_BE_REMOVED` | Indicates issues with a physical disk. |
 | `Available size is less than 12%/9%/6%` | Free space on the physical disk is running out. |
 | `PDisk is not available` | A physical disk is not available. |
 | **STORAGE_NODE** ||
-| `Storage node is not available` | A node with disks is not available. |
+| `Storage node is not available` | A storage node is not available. |
 | **COMPUTE** ||
 | `There are no compute nodes` | The database has no nodes to start the tablets. </br>Unable to determine `COMPUTE_NODE` issues below. |
 | `Compute has issues with system tablets` | These issues depend solely on the underlying `SYSTEM_TABLET` layer. |
 | `Some nodes are restarting too often` | These issues depend solely on the underlying `NODE_UPTIME` layer. |
 | `Compute is overloaded` | These issues depend solely on the underlying `COMPUTE_POOL` layer. |
 | `Compute quota usage` | These issues depend solely on the underlying `COMPUTE_QUOTA` layer. |
-| `Compute has issues with tablets`| These issues depend solely on the underlying `TABLET` layer. |
+| `Compute has issues with tablets` | These issues depend solely on the underlying `TABLET` layer. |
 | **COMPUTE_QUOTA** ||
 | `Paths quota usage is over 90%/99%/Paths quota exhausted` </br>`Shards quota usage is over 90%/99%/Shards quota exhausted` | Quotas exhausted |
 | **COMPUTE_NODE** | *This layer has no specific issues.* |