diff --git a/src/backend/executor/execPartition.c b/src/backend/executor/execPartition.c
index 901dd435ef..40e3c07693 100644
--- a/src/backend/executor/execPartition.c
+++ b/src/backend/executor/execPartition.c
@@ -2155,8 +2155,8 @@ InitPartitionPruneContext(PartitionPruneContext *context,
  * Current values of the indexes present in PartitionPruneState count all the
  * subplans that would be present before initial pruning was done.  If initial
  * pruning got rid of some of the subplans, any subsequent pruning passes will
- * will be looking at a different set of target subplans to choose from than
- * those in the pre-initial-pruning set, so the maps in PartitionPruneState
+ * be looking at a different set of target subplans to choose from than those
+ * in the pre-initial-pruning set, so the maps in PartitionPruneState
  * containing those indexes must be updated to reflect the new indexes of
  * subplans in the post-initial-pruning set.
  */
diff --git a/src/backend/utils/activity/pgstat.c b/src/backend/utils/activity/pgstat.c
index b0ff21b690..9e3b643a2c 100644
--- a/src/backend/utils/activity/pgstat.c
+++ b/src/backend/utils/activity/pgstat.c
@@ -556,7 +556,7 @@ pgstat_initialize(void)
  * suggested idle timeout is returned. Currently this is always
  * PGSTAT_IDLE_INTERVAL (10000ms). Callers can use the returned time to set up
  * a timeout after which to call pgstat_report_stat(true), but are not
- * required to to do so.
+ * required to do so.
  *
  * Note that this is called only when not within a transaction, so it is fair
  * to use transaction stop time as an approximation of current time.
diff --git a/src/backend/utils/activity/pgstat_replslot.c b/src/backend/utils/activity/pgstat_replslot.c
index b77c05ab5f..2039ac3147 100644
--- a/src/backend/utils/activity/pgstat_replslot.c
+++ b/src/backend/utils/activity/pgstat_replslot.c
@@ -8,13 +8,13 @@
  * storage implementation and the details about individual types of
  * statistics.
  *
- * Replication slot stats work a bit different than other other
- * variable-numbered stats. Slots do not have oids (so they can be created on
- * physical replicas). Use the slot index as object id while running. However,
- * the slot index can change when restarting. That is addressed by using the
- * name when (de-)serializing. After a restart it is possible for slots to
- * have been dropped while shut down, which is addressed by not restoring
- * stats for slots that cannot be found by name when starting up.
+ * Replication slot stats work a bit different than other variable-numbered
+ * stats. Slots do not have oids (so they can be created on physical
+ * replicas). Use the slot index as object id while running. However, the slot
+ * index can change when restarting. That is addressed by using the name when
+ * (de-)serializing. After a restart it is possible for slots to have been
+ * dropped while shut down, which is addressed by not restoring stats for
+ * slots that cannot be found by name when starting up.
  *
  * Copyright (c) 2001-2022, PostgreSQL Global Development Group
  *
diff --git a/src/test/ssl/t/SSL/Server.pm b/src/test/ssl/t/SSL/Server.pm
index 62f54dcbf1..9520578e7d 100644
--- a/src/test/ssl/t/SSL/Server.pm
+++ b/src/test/ssl/t/SSL/Server.pm
@@ -257,7 +257,7 @@ The certificate file to use. Implementation is SSL backend specific.
 
 =item keyfile => B<value>
 
-The private key to to use. Implementation is SSL backend specific.
+The private key to use. Implementation is SSL backend specific.
 
 =item crlfile => B<value>