From f9b16643b306a32b6180c56f1b5d1558d945f718 Mon Sep 17 00:00:00 2001
From: Kristopher Watts
 <108431167+kris-watts-gravwell@users.noreply.github.com>
Date: Tue, 28 Jan 2025 08:43:13 -0700
Subject: [PATCH] Update configuration/replication.md

Co-authored-by: Ashley Wade <107071905+ashnwade@users.noreply.github.com>
---
 configuration/replication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configuration/replication.md b/configuration/replication.md
index 5f687661..d3f8d215 100644
--- a/configuration/replication.md
+++ b/configuration/replication.md
@@ -45,7 +45,7 @@ Each node specifies the other nodes in its `Peer` fields.
 The replication engine relies on an internal database to maintain the state of the replication system and all peers. If no `Database-Path` is defined, the system will deploy the database to a file named `replication.db` within the `Storage-Location` directory.
 
 ```{attention}
-The replication database is critical to the healthy operation of the replication system, it will perform frequent file syncs and often operates in synchronous IO mode.  If your replication storage system is slow or employs transparent compression it is reccomended that the replication database be stored on a high IOP storage array.  The replication database is typically only a few MB in size, even on very large deployments.
+The replication database is critical to the healthy operation of the replication system. It will perform frequent file syncs and often operates in synchronous IO mode.  If your replication storage system is slow or employs transparent compression, it is recommended that the replication database be stored on a high IOP storage array.  The replication database is typically only a few MB in size, even on very large deployments.
 ```
 
 ## Region Aware Deployment