Fix typos, remove unused docker compose volume reference

Author: pcholakov

docs/deploy/server/cluster/deployment.mdx

@@ -25,7 +25,7 @@ This page describes how you can deploy a distributed Restate cluster.
 </Admonition>
 
 <Admonition type="caution">
-    Snapshots are essential to support safe log trimming and also allow you to set partition replication to a subset of all cluster nodes, while still allowing for fast partition fail-over to to any live node. Snapshots are also necessary to add more nodes in the future.
+    Snapshots are essential to support safe log trimming and also allow you to set partition replication to a subset of all cluster nodes, while still allowing for fast partition fail-over to any live node. Snapshots are also necessary to add more nodes in the future.
 </Admonition>
 
 To deploy a distributed Restate cluster without external dependencies, you need to configure the following settings in your [server configuration](/operate/configuration/server):

docs/guides/cluster.mdx

@@ -89,8 +89,6 @@ services:
 
   minio:
     image: quay.io/minio/minio
-    # volumes:
-    #   - object-store:/data
     entrypoint: "/bin/sh"
     # Ensure a bucket called "restate" exists on startup:
     command: "-c 'mkdir -p /data/restate && /usr/bin/minio server --quiet /data'"

docs/operate/snapshots.mdx

@@ -16,7 +16,7 @@ import Admonition from '@theme/Admonition';
 </Admonition>
 
 <Admonition type="caution">
-    Snapshots are essential to support safe log trimming and also allow you to set partition replication to a subset of all cluster nodes, while still allowing for fast partition fail-over to to any live node. Snapshots are also necessary to add more nodes in the future.
+    Snapshots are essential to support safe log trimming and also allow you to set partition replication to a subset of all cluster nodes, while still allowing for fast partition fail-over to any live node. Snapshots are also necessary to add more nodes in the future.
 </Admonition>
 
 Restate workers can be configured to periodically publish snapshots of their partition state to a shared destination. Snapshots are not necessarily backups. Rather, snapshots allow nodes that had not previously served a partition to bootstrap a copy of its state. Without snapshots, placing a partition processor on a node that wasn't previously a follower would require the full replay of that partition's log. Replaying the log might take a long time - and is impossible if the log gets trimmed.