Fix according to remarks

docs/arguments.md

@@ -170,6 +170,16 @@ Environment Variable: WATCHTOWER_NO_PULL
              Default: false
 ``` 
 
+## Without sending a startup message
+Do not send a send a message after watchtower started. Otherwise there will be an info-level notification. 
+
+```
+            Argument: --no-startup-message
+Environment Variable: WATCHTOWER_NO_STARTUP_MESSAGE
+                Type: Boolean
+             Default: false
+```
+
 ## Run once
 Run an update attempt against a container name list one time immediately and exit.
 

docs/notifications.md

@@ -18,7 +18,6 @@ The types of notifications to send are set by passing a comma-separated list of
 ## Settings
 
 - `--notifications-level` (env. `WATCHTOWER_NOTIFICATIONS_LEVEL`): Controls the log level which is used for the notifications. If omitted, the default log level is `info`. Possible values are: `panic`, `fatal`, `error`, `warn`, `info` or `debug`.
-- `--no-startup-message` (env. `WATCHTOWER_NOTIFICATION_NO_STARTUP_MESSAGE`): Prevents watchtower from sending a startup message.
 
 ## Available services
 

internal/flags/flags.go

@@ -52,6 +52,12 @@ func RegisterSystemFlags(rootCmd *cobra.Command) {
 		viper.GetBool("WATCHTOWER_NO_RESTART"),
 		"do not restart any containers")
 
+	flags.BoolP(
+		"no-startup-message",
+		"",
+		viper.GetBool("WATCHTOWER_NO_STARTUP_MESSAGE"),
+		"Prevents watchtower from sending a startup message")
+
 	flags.BoolP(
 		"cleanup",
 		"c",
@@ -123,12 +129,6 @@ func RegisterNotificationFlags(rootCmd *cobra.Command) {
 		viper.GetString("WATCHTOWER_NOTIFICATIONS_LEVEL"),
 		"The log level used for sending notifications. Possible values: panic, fatal, error, warn, info or debug")
 
-	flags.BoolP(
-		"no-startup-message",
-		"",
-		viper.GetBool("WATCHTOWER_NOTIFICATION_NO_STARTUP_MESSAGE"),
-		"Prevents watchtower from sending a startup message")
-
 	flags.StringP(
 		"notification-email-from",
 		"",