From cfbd975e4a31b5bebb42de75d1e742044d73a5d7 Mon Sep 17 00:00:00 2001
From: Sanam <31341013+sanamhub@users.noreply.github.com>
Date: Fri, 21 Jul 2023 15:10:31 +0545
Subject: [PATCH] chore: fix typo

---
 MaintenanceSolution/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MaintenanceSolution/README.md b/MaintenanceSolution/README.md
index 9e03e678..fa045cc7 100644
--- a/MaintenanceSolution/README.md
+++ b/MaintenanceSolution/README.md
@@ -24,7 +24,7 @@ Here's the detail on what these steps do:
 
 - **3_job_AdaptiveIndexDefrag**
   - Creates a daily job for the AdaptiveIndexDefrag procedure, named “Daily Index Defrag”. It will also notify the previously created operator on the job outcome.
-  - Find some of the most common (default) names for Microsoft shipped databases (step “DB Exceptions”), to add the to the permanent exclusion list, if not already there. For example, SharePoint grooms its own databases, so we shou.ld exclude them from any other automated maintenance task. If the AdaptiveIndexDefrag procedure was NOT created in MSDB, simply replace all references to MSDB for whatever database name you chose.
+  - Find some of the most common (default) names for Microsoft shipped databases (step “DB Exceptions”), to add the to the permanent exclusion list, if not already there. For example, SharePoint grooms its own databases, so we should exclude them from any other automated maintenance task. If the AdaptiveIndexDefrag procedure was NOT created in MSDB, simply replace all references to MSDB for whatever database name you chose.
   - Execute the AdaptiveIndexDefrag procedure (step “Daily Index Defrag”).
   - Purge all historic log data for the index defrag executions using default 90 days (step “Purge Log”).