From 1ed78514c5d8786fb5cb9f58c446dbdc797935ee Mon Sep 17 00:00:00 2001
From: Abdullah Farid <abdullah@farid.top>
Date: Sat, 2 Mar 2024 13:19:11 +0000
Subject: [PATCH] Fix spelling mistakes

---
 docs/arguments.md                  | 2 +-
 docs/running-multiple-instances.md | 2 +-
 internal/flags/flags_test.go       | 4 ++--
 pkg/notifications/notifier_test.go | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/arguments.md b/docs/arguments.md
index d7ed0b0..03941a0 100644
--- a/docs/arguments.md
+++ b/docs/arguments.md
@@ -448,7 +448,7 @@ Returns a success exit code to enable usage with docker `HEALTHCHECK`. This chec
             Argument: --health-check
 ```
 
-## Programatic Output (porcelain)
+## Programmatic Output (porcelain)
 
 Writes the session results to STDOUT using a stable, machine-readable format (indicated by the argument VERSION).  
   
diff --git a/docs/running-multiple-instances.md b/docs/running-multiple-instances.md
index 5a82c80..1c18fbd 100644
--- a/docs/running-multiple-instances.md
+++ b/docs/running-multiple-instances.md
@@ -3,7 +3,7 @@ By default, Watchtower will clean up other instances and won't allow multiple in
 !!! note
     - Multiple instances can't run with the same scope;
     - An instance without a scope will clean up other running instances, even if they have a defined scope;
-    - Supplying `none` as the scope will treat `com.centurylinklabs.watchtower.scope=none`, `com.centurylinklabs.watchtower.scope=` and the lack of a `com.centurylinklabs.watchtower.scope` label as the scope `none`. This effectly enables you to run both scoped and unscoped watchtower instances on the same machine.
+    - Supplying `none` as the scope will treat `com.centurylinklabs.watchtower.scope=none`, `com.centurylinklabs.watchtower.scope=` and the lack of a `com.centurylinklabs.watchtower.scope` label as the scope `none`. This effectively enables you to run both scoped and unscoped watchtower instances on the same machine.
 
 To define an instance monitoring scope, use the `--scope` argument or the `WATCHTOWER_SCOPE` environment variable on startup and set the `com.centurylinklabs.watchtower.scope` label with the same value for the containers you want to include in this instance's scope (including the instance itself).
 
diff --git a/internal/flags/flags_test.go b/internal/flags/flags_test.go
index 2856456..ded670b 100644
--- a/internal/flags/flags_test.go
+++ b/internal/flags/flags_test.go
@@ -278,9 +278,9 @@ func TestProcessFlagAliasesInvalidPorcelaineVersion(t *testing.T) {
 	})
 }
 
-func TestFlagsArePrecentInDocumentation(t *testing.T) {
+func TestFlagsArePresentInDocumentation(t *testing.T) {
 
-	// Legacy notifcations are ignored, since they are (soft) deprecated
+	// Legacy notifications are ignored, since they are (soft) deprecated
 	ignoredEnvs := map[string]string{
 		"WATCHTOWER_NOTIFICATION_SLACK_ICON_EMOJI": "legacy",
 		"WATCHTOWER_NOTIFICATION_SLACK_ICON_URL":   "legacy",
diff --git a/pkg/notifications/notifier_test.go b/pkg/notifications/notifier_test.go
index 96d513c..ac2cecd 100644
--- a/pkg/notifications/notifier_test.go
+++ b/pkg/notifications/notifier_test.go
@@ -28,7 +28,7 @@ var _ = Describe("notifications", func() {
 
 			Expect(notif.GetNames()).To(BeEmpty())
 		})
-		When("title is overriden in flag", func() {
+		When("title is overridden in flag", func() {
 			It("should use the specified hostname in the title", func() {
 				command := cmd.NewRootCommand()
 				flags.RegisterNotificationFlags(command)