Rewording

Author: pcholakov

docs/operate/troubleshooting.mdx

@@ -32,7 +32,7 @@ To recover from this situation, you need to make available a snapshot of the par
 #### Recovery procedure
 
 <Step stepLabel="1" title="Identify whether a snapshot repository is configured and accessible">
-If a snapshot repository is set up on other nodes in the cluster, and simply not configured on the node where you are seeing the partition processor startup errors, correct the configuration on the new node - refer to [Configuring Snapshots](/operate/snapshots#configuring-snapshots).  If you have not yet set up a snapshot repository, please do so now. If it is absolutely not possible to use an object store to set up a repository, you may export snapshots to the local filesystem and manually transfer it to the affected node - skip to step `2b`.
+If a snapshot repository is set up on other nodes in the cluster, and simply not configured on the node where you are seeing the partition processor startup errors, correct the configuration on the new node - refer to [Configuring Snapshots](/operate/snapshots#configuring-snapshots). If you have not yet set up a snapshot repository, please do so now. If it is impossible to use an object store to host the snapshots repository, you can export snapshots to a local filesystem and manually transfer them to other nodes - skip to step `2b`.
 
 In your server configuration, you should have a snapshot path specified as follows: