From 68c3a906b116ab0eaf91ad85375b8b852aab049e Mon Sep 17 00:00:00 2001 From: petems Date: Thu, 13 Jun 2019 15:37:55 +0100 Subject: [PATCH] Minor spelling fixes `docker run -v $(pwd):/scripts --workdir=/scripts nickg/misspell:latest misspell -w -source=text website/` --- website/source/docs/docker/configuration.html.md | 2 +- website/source/docs/experimental/index.html.md | 2 +- .../source/docs/installation/backwards-compatibility.html.md | 2 +- website/source/docs/triggers/configuration.html.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/website/source/docs/docker/configuration.html.md b/website/source/docs/docker/configuration.html.md index 0a9f94746..c3be69be4 100644 --- a/website/source/docs/docker/configuration.html.md +++ b/website/source/docs/docker/configuration.html.md @@ -23,7 +23,7 @@ One of the following settings is required when using the Docker provider: * `git_repo` (string) - The URL of a git repository to build the image from. Supports pulling specific tags, branches and revision, consult the - [docker documenation](https://docs.docker.com/engine/reference/commandline/build/#/git-repositories) + [docker documentation](https://docs.docker.com/engine/reference/commandline/build/#/git-repositories) for more information. ### Optional diff --git a/website/source/docs/experimental/index.html.md b/website/source/docs/experimental/index.html.md index cb3d7818c..5d0c7d34b 100644 --- a/website/source/docs/experimental/index.html.md +++ b/website/source/docs/experimental/index.html.md @@ -10,7 +10,7 @@ description: |- Some features that aren't ready for release can be enabled through this feature flag. There are a couple of different ways of going about enabling these features. -It is also worth noting that Vagrant will not validate the existance of a feature +It is also worth noting that Vagrant will not validate the existence of a feature flag. For example if you are on Linux or Mac, and you wish to enable every single experimental feature, you can set the flag diff --git a/website/source/docs/installation/backwards-compatibility.html.md b/website/source/docs/installation/backwards-compatibility.html.md index 454a8cf38..f0dd51f94 100644 --- a/website/source/docs/installation/backwards-compatibility.html.md +++ b/website/source/docs/installation/backwards-compatibility.html.md @@ -3,7 +3,7 @@ layout: "docs" page_title: "Backwards Compatibility" sidebar_current: "installation-backwards-compatibility" description: |- - Vagrant makes a very strict backwards-compatability promise. + Vagrant makes a very strict backwards-compatibility promise. --- # Backwards Compatibility diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md index 62e62ae1d..9156774dd 100644 --- a/website/source/docs/triggers/configuration.html.md +++ b/website/source/docs/triggers/configuration.html.md @@ -121,7 +121,7 @@ end Triggers _without_ the type option will run before or after a Vagrant guest. -Older Vagrant versions will unfortunetly not be able to properly parse the new +Older Vagrant versions will unfortunately not be able to properly parse the new `:type` option. If you are worried about older clients failing to parse your Vagrantfile, you can guard the new trigger based on the version of Vagrant: