diff --git a/docs/concepts/architecture.rst b/docs/concepts/architecture.rst
index 6727bd61db..9f080f7532 100644
--- a/docs/concepts/architecture.rst
+++ b/docs/concepts/architecture.rst
@@ -32,7 +32,7 @@ Flyte components are separated into 3 logical planes. The planes are summarized
 |                   | It stores information such as current and past running workflows, and provides that information upon request. |
 |                   | It also accepts requests to execute workflows, but offloads the work to the Data Plane.                       |
 +-------------------+---------------------------------------------------------------------------------------------------------------+
-| **Data Plane**    | The sole responsibility of the the Data Plane is to fulfill workflows.                                        |
+| **Data Plane**    | The sole responsibility of the Data Plane is to fulfill workflows.                                            |
 |                   | It accepts workflow requests from the Control Plane and guides the workflow to completion,                    |
 |                   | launching tasks on a cluster of machines as necessary based on the workflow graph.                            |
 |                   | It sends status events back to the control plane so the information can be stored and surfaced to end-users.  |
diff --git a/docs/deployment/configuration/monitoring.rst b/docs/deployment/configuration/monitoring.rst
index 7b0d9ddc0b..48239288f4 100644
--- a/docs/deployment/configuration/monitoring.rst
+++ b/docs/deployment/configuration/monitoring.rst
@@ -133,7 +133,7 @@ This is especially true if you plan to use the Service Monitors provided by the
 
 .. note::
 
-   By default, the ``ServiceMonitor`` is configured with a ``scrapeTimeout`` of 30s and and ``interval`` of 60s. You can customize these values if needed.
+   By default, the ``ServiceMonitor`` is configured with a ``scrapeTimeout`` of 30s and ``interval`` of 60s. You can customize these values if needed.
 
 With the above configuration in place you should be able to import the dashboards in your Grafana instance.
 
diff --git a/flytectl/docs/source/gen/flytectl_update_project.rst b/flytectl/docs/source/gen/flytectl_update_project.rst
index 63a3c4ebaf..ce203b736b 100644
--- a/flytectl/docs/source/gen/flytectl_update_project.rst
+++ b/flytectl/docs/source/gen/flytectl_update_project.rst
@@ -53,7 +53,7 @@ Then, pass it in using the *file* flag:
 
 To archive or activate (unarchive) a project using a *yaml* file:
 
-* Add a state field, with a value of *0* for activated (unarchived) or *1* for archived, at the top level of the the *yaml* file.
+* Add a state field, with a value of *0* for activated (unarchived) or *1* for archived, at the top level of the *yaml* file.
 
 * Add the *archive* flag to the command.