diff --git a/doc/modules/cassandra/pages/architecture/accord-architecture.adoc b/doc/modules/cassandra/pages/architecture/accord-architecture.adoc
index 201abd861ec6..4acb2395d6c4 100644
--- a/doc/modules/cassandra/pages/architecture/accord-architecture.adoc
+++ b/doc/modules/cassandra/pages/architecture/accord-architecture.adoc
@@ -245,7 +245,7 @@ history, and are used for invalidating older `TxnId`s, so that a newly
 bootstrapped node may have a complete log as of a point in time `TxnId`,
 and replicas could purge/GC earlier transaction metadata.
 
-SyncPoints are not expected to be processed by the the whole cluster,
+SyncPoints are not expected to be processed by the whole cluster,
 and we do not want transaction processing to be held up, so while these
 are processed much like a transaction, they are invisible to real
 transactions which may proceed before SyncPoint is witnessed by the node
diff --git a/doc/modules/cassandra/pages/developing/cql/ddl.adoc b/doc/modules/cassandra/pages/developing/cql/ddl.adoc
index 6b42eabc5f6e..616bcfa06bef 100644
--- a/doc/modules/cassandra/pages/developing/cql/ddl.adoc
+++ b/doc/modules/cassandra/pages/developing/cql/ddl.adoc
@@ -33,7 +33,7 @@ equivalent to `mytable`) but case sensitivity can be forced by using
 double-quotes (`"myTable"` is different from `mytable`).
 
 Further, a table is always part of a keyspace and a table name can be
-provided fully-qualified by the keyspace it is part of. If is is not
+provided fully-qualified by the keyspace it is part of. If it is not
 fully-qualified, the table is assumed to be in the _current_ keyspace
 (see xref:cassandra:developing/cql/ddl.adoc#use-statement[USE] statement).
 
diff --git a/doc/modules/cassandra/pages/developing/data-modeling/data-modeling_refining.adoc b/doc/modules/cassandra/pages/developing/data-modeling/data-modeling_refining.adoc
index d7ea619c88f1..e6231fcbd232 100644
--- a/doc/modules/cassandra/pages/developing/data-modeling/data-modeling_refining.adoc
+++ b/doc/modules/cassandra/pages/developing/data-modeling/data-modeling_refining.adoc
@@ -23,7 +23,7 @@ In order to calculate the size of partitions, use the following formula:
 
 The number of values (or cells) in the partition (N~v~) is equal to the
 number of static columns (N~s~) plus the product of the number of rows
-(N~r~) and the number of of values per row. The number of values per row
+(N~r~) and the number of values per row. The number of values per row
 is defined as the number of columns (N~c~) minus the number of primary
 key columns (N~pk~) and static columns (N~s~).
 
diff --git a/doc/modules/cassandra/pages/managing/operating/repair.adoc b/doc/modules/cassandra/pages/managing/operating/repair.adoc
index d7eaba171125..baf6863189d6 100644
--- a/doc/modules/cassandra/pages/managing/operating/repair.adoc
+++ b/doc/modules/cassandra/pages/managing/operating/repair.adoc
@@ -1,6 +1,6 @@
 = Repair
 
-Cassandra is designed to remain available if one of it's nodes is down
+Cassandra is designed to remain available if one of its nodes is down
 or unreachable. However, when a node is down or unreachable, it needs to
 eventually discover the writes it missed. Hints attempt to inform a node
 of missed writes, but are a best effort, and aren't guaranteed to inform
@@ -104,7 +104,7 @@ providing enough slack to allow for delays.
   default, incremental repairs are estimated, add the `--full` flag to
   estimate a full repair.
 `-vd, --validate`::
-  Verifies that the repaired data is the same across all nodes. Similiar
+  Verifies that the repaired data is the same across all nodes. Similar
   to `--preview`, this builds and compares merkle trees of repaired
   data, but doesn't do any streaming. This is useful for
   troubleshooting. If this shows that the repaired data is out of sync,