diff --git a/documentation/examples/prometheus-dockerswarm.yml b/documentation/examples/prometheus-dockerswarm.yml
index efb228fa9f..ccbaf2630f 100644
--- a/documentation/examples/prometheus-dockerswarm.yml
+++ b/documentation/examples/prometheus-dockerswarm.yml
@@ -10,7 +10,7 @@ scrape_configs:
 
   # Create a job for Docker daemons.
   #
-  # This exemple requires Docker daemons to be configured to expose
+  # This example requires Docker daemons to be configured to expose
   # Prometheus metrics, as documented here:
   # https://docs.docker.com/config/daemon/prometheus/
   - job_name: 'docker'
diff --git a/tsdb/chunks/head_chunks_test.go b/tsdb/chunks/head_chunks_test.go
index 70ffaba59a..bfb4262ad1 100644
--- a/tsdb/chunks/head_chunks_test.go
+++ b/tsdb/chunks/head_chunks_test.go
@@ -261,7 +261,7 @@ func TestHeadReadWriter_Truncate(t *testing.T) {
 // TestHeadReadWriter_Truncate_NoUnsequentialFiles tests
 // that truncation leaves no unsequential files on disk, mainly under the following case
 // * There is an empty file in between the sequence while the truncation
-//   deletes files only upto a sequence before that (i.e. stops deleting
+//   deletes files only up to a sequence before that (i.e. stops deleting
 //   after it has found a file that is not deletable).
 // This tests https://github.com/prometheus/prometheus/issues/7412 where
 // the truncation used to check all the files for deletion and end up
diff --git a/tsdb/head.go b/tsdb/head.go
index 759d983b11..60c26a4183 100644
--- a/tsdb/head.go
+++ b/tsdb/head.go
@@ -2323,7 +2323,7 @@ func (mc *mmappedChunk) OverlapsClosedInterval(mint, maxt int64) bool {
 // SeriesLifecycleCallback specifies a list of callbacks that will be called during a lifecycle of a series.
 // It is always a no-op in Prometheus and mainly meant for external users who import TSDB.
 // All the callbacks should be safe to be called concurrently.
-// It is upto the user to implement soft or hard consistency by making the callbacks
+// It is up to the user to implement soft or hard consistency by making the callbacks
 // atomic or non-atomic. Atomic callbacks can cause degradation performance.
 type SeriesLifecycleCallback interface {
 	// PreCreation is called before creating a series to indicate if the series can be created.