Update _index.md

rqlite · Dec 8, 2023 · ceaf3cb · ceaf3cb
1 parent 4348f6c
commit ceaf3cb
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/en/docs/Guides/backup/_index.md b/content/en/docs/Guides/backup/_index.md
@@ -85,7 +85,7 @@ rqlite supports loading a node directly from two sources, either of which can be
 - **SQLite dump in text format**. This is another convenient manner to initialize a system from an existing SQLite database (or other database). In constrast to loading an actual SQLite file, the behavior of this type of load operation is **undefined** if there is already data loaded into your rqlite cluster.  **Note that if your source database is large, the operation can be quite slow.** If you find the restore times to be too long, you should first load the SQL statements directly into a SQLite database, and then restore rqlite using the resulting SQLite database file.
 
 ### Performing a restore
-The most robust process for restoring a cluster is to **restore a single standalone node**, and then join other nodes to it. If you decide instead to restore a multi-node cluster, it is strongly recommended that the cluster be **freshly deployed, without any pre-existing data**. This is the easiest state to manage and monitor -- and if a _Restore_ operation should fail (which is quite unlikely) it is best to start again with a new cluster. Finally, make sure there sure there is **no other write traffic being sent to your rqlite system** while you are restoring from a backup.
+The most robust process is to **restore a single standalone node**, and then join other nodes to the first node. If you decide instead to restore a multi-node cluster, it is strongly recommended that the cluster be **freshly deployed, without any pre-existing data**. This is the easiest state to manage and monitor -- and if a _Restore_ operation should fail (which is quite unlikely) it is best to start again with a new cluster. Finally, make sure there is **no other write traffic being sent to your rqlite system** while you are restoring from a backup.
 
 The following examples show a trivial database being generated by `sqlite3` and then loaded into a rqlite node listening on localhost. The first example shows you how to do it via a direct call to the HTTP API, the second example shows you how to do it using the [rqlite shell](https://rqlite.io/docs/cli/).