Doc fixes (#5211)

* exit code: skaffold.yaml was found exit code is 103 * change fsnotify to notify: use same name as underlying package.
GoogleContainerTools · Jan 13, 2021 · 71d001b · 71d001b
1 parent 2efeb55
commit 71d001b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/content/en/docs/pipeline-stages/init.md b/docs/content/en/docs/pipeline-stages/init.md
@@ -194,5 +194,5 @@ When `skaffold init` fails, it exits with an code that depends on the error:
 | ---- | --- |
 | 101 | No build configuration could be found |
 | 102 | No k8s manifest could be found or generated |
-| 102 | An existing skaffold.yaml was found |
+| 103 | An existing skaffold.yaml was found |
 | 104 | Couldn't match builder with image names automatically |
diff --git a/docs/content/en/docs/workflows/dev.md b/docs/content/en/docs/workflows/dev.md
@@ -31,7 +31,7 @@ The actions performed by Skaffold during the dev loop have precedence over one a
 
 Skaffold computes the dependencies for each artifact based on the builder being used, and the root directory of the artifact. Once all source file dependencies are computed, in `dev` mode, Skaffold will continuously watch these files for changes in the background, and conditionally re-run the loop when changes are detected.
 
-By default, Skaffold uses `fsnotify` to monitor events on the local filesystem. Skaffold also supports a `polling` mode where the filesystem is checked for changes on a configurable interval, or a `manual` mode, where Skaffold waits for user input to check for file changes. These watch modes can be configured through the `--trigger` flag.
+By default, Skaffold uses `notify` to monitor events on the local filesystem. Skaffold also supports a `polling` mode where the filesystem is checked for changes on a configurable interval, or a `manual` mode, where Skaffold waits for user input to check for file changes. These watch modes can be configured through the `--trigger` flag.
 
 ## Control API