diff --git a/_posts/2024-09-24-creating-a-new-database-integration-with-data-prepper.markdown b/_posts/2024-09-24-creating-a-new-database-integration-with-data-prepper.markdown
index f5cf0594e..79e1935c8 100644
--- a/_posts/2024-09-24-creating-a-new-database-integration-with-data-prepper.markdown
+++ b/_posts/2024-09-24-creating-a-new-database-integration-with-data-prepper.markdown
@@ -106,7 +106,7 @@ public void run() {
 }
 ```
 
-The key components and workflow in the code for implementing source coordination in Data Prepper are as follows:
+The key components and code workflow for implementing source coordination in Data Prepper are as follows:
 
 1. Upon starting Data Prepper, a leader partition is established. See the [code reference](https://github.com/graytaylor0/data-prepper/blob/6e38dead8e9beca089381519654f329b82524b9d/data-prepper-plugins/sample-source-coordination-source/src/main/java/SampleSource.java#L41)). The single leader partition is assigned to the Data Prepper node that successfully calls `acquireAvailablePartition(LeaderPartition.PARTITION_TYPE)`, assigning it the task of identifying new database files.
 2. When a Data Prepper node owns the leader partition, it queries the hypothetical database and creates new partitions in the source coordination store, enabling all nodes running this source to access these database file partitions.