13 files changed, 16 insertions, 16 deletions

diff --git a/docs/markdown/Build-options.md b/docs/markdown/Build-options.md
index af4a58a..93e3326 100644
--- a/docs/markdown/Build-options.md
+++ b/docs/markdown/Build-options.md
@@ -183,7 +183,7 @@ issue the following command:
 prefix = get_option('prefix')
 ```
 
-It should be noted that you can not set option values in your Meson
+It should be noted that you cannot set option values in your Meson
 scripts. They have to be set externally with the `meson configure`
 command line tool. Running `meson configure` without arguments in a
 build dir shows you all options you can set.
diff --git a/docs/markdown/Build-targets.md b/docs/markdown/Build-targets.md
index 83f959f..780595c 100644
--- a/docs/markdown/Build-targets.md
+++ b/docs/markdown/Build-targets.md
@@ -9,7 +9,7 @@ Meson provides four kinds of build targets: executables, libraries
 the build configuration time), static libraries, and shared libraries.
 They are created with the commands `executable`, `library`,
 `static_library` and `shared_library`, respectively. All objects created
-in this way are **immutable**. That is, you can not change any aspect of
+in this way are **immutable**. That is, you cannot change any aspect of
 them after they have been constructed. This ensures that all information
 pertaining to a given build target is specified in one well defined
 place.
diff --git a/docs/markdown/Compiler-properties.md b/docs/markdown/Compiler-properties.md
index de28d9b..6d04c8b 100644
--- a/docs/markdown/Compiler-properties.md
+++ b/docs/markdown/Compiler-properties.md
@@ -228,4 +228,4 @@ has_special_flags = [[#compiler.has_argument]]('-Wspecialthing')
 ```
 
 *Note*: some compilers silently swallow command line arguments they do
-not understand. Thus this test can not be made 100% reliable.
+not understand. Thus this test cannot be made 100% reliable.
diff --git a/docs/markdown/Design-rationale.md b/docs/markdown/Design-rationale.md
index a3bd5bb..67fec0a 100644
--- a/docs/markdown/Design-rationale.md
+++ b/docs/markdown/Design-rationale.md
@@ -240,7 +240,7 @@ project('pch demo', 'cxx')
 executable('myapp', 'myapp.cpp', pch : 'pch/myapp.hh')
 ```
 
-The main reason other build systems can not provide pch support this
+The main reason other build systems cannot provide pch support this
 easily is because they don't enforce certain best practices. Due to
 the way include paths work, it is impossible to provide pch support
 that always works with both in-source and out-of-source
diff --git a/docs/markdown/External-commands.md b/docs/markdown/External-commands.md
index 026ed54..07445ac 100644
--- a/docs/markdown/External-commands.md
+++ b/docs/markdown/External-commands.md
@@ -42,7 +42,7 @@ Meson will autodetect scripts with a shebang line and run them with
 the executable/interpreter specified in it both on Windows and on
 Unixes.
 
-Note that you can not pass your command line as a single string. That
+Note that you cannot pass your command line as a single string. That
 is, calling `run_command('do_something foo bar')` will not work. You
 must either split up the string into separate arguments or pass the
 split command as an array. It should also be noted that Meson will not
diff --git a/docs/markdown/FAQ.md b/docs/markdown/FAQ.md
index d3e3d0a..8bcea20 100644
--- a/docs/markdown/FAQ.md
+++ b/docs/markdown/FAQ.md
@@ -62,7 +62,7 @@ executable('myprog', sources : '*.cpp') # This does NOT work!
 ```
 
 Meson does not support this syntax and the reason for this is simple.
-This can not be made both reliable and fast. By reliable we mean that
+This cannot be made both reliable and fast. By reliable we mean that
 if the user adds a new source file to the subdirectory, Meson should
 detect that and make it part of the build automatically.
 
@@ -149,7 +149,7 @@ subdir('tests') # test binaries would link against the library here
 ## Why is there not a Make backend?
 
 Because Make is slow. This is not an implementation issue, Make simply
-can not be made fast. For further info we recommend you read [this
+cannot be made fast. For further info we recommend you read [this
 post](http://neugierig.org/software/chromium/notes/2011/02/ninja.html)
 by Evan Martin, the author of Ninja. Makefiles also have a syntax that
 is very unpleasant to write which makes them a big maintenance burden.
@@ -348,7 +348,7 @@ projects attempting to do just this:
 Meson needs to know several details about each compiler in order to
 compile code with it. These include things such as which compiler
 flags to use for each option and how to detect the compiler from its
-output. This information can not be input via a configuration file,
+output. This information cannot be input via a configuration file,
 instead it requires changes to Meson's source code that need to be
 submitted to Meson master repository. In theory you can run your own
 forked version with custom patches, but that's not good use of your
diff --git a/docs/markdown/Feature-autodetection.md b/docs/markdown/Feature-autodetection.md
index 2371226..bd6be75 100644
--- a/docs/markdown/Feature-autodetection.md
+++ b/docs/markdown/Feature-autodetection.md
@@ -17,7 +17,7 @@ automatically.
 
 If you do not wish to use Ccache for some reason, just specify your
 compiler with environment variables `CC` and/or `CXX` when first
-running Meson (remember that once specified the compiler can not be
+running Meson (remember that once specified the compiler cannot be
 changed). Meson will then use the specified compiler without Ccache.
 
 Coverage
diff --git a/docs/markdown/Generating-sources.md b/docs/markdown/Generating-sources.md
index 91e0930..8b1b44e 100644
--- a/docs/markdown/Generating-sources.md
+++ b/docs/markdown/Generating-sources.md
@@ -179,7 +179,7 @@ gen2 = generator(someprog,
                  arguments : ['--out_dir=@BUILD_DIR@', '@INPUT@'])
 ```
 
-In this case you can not use the plain `@OUTPUT@` variable, as it
+In this case you cannot use the plain `@OUTPUT@` variable, as it
 would be ambiguous. This program only needs to know the output
 directory, it will generate the file names by itself.
 
diff --git a/docs/markdown/Mixing-build-systems.md b/docs/markdown/Mixing-build-systems.md
index 6830064..73f91b7 100644
--- a/docs/markdown/Mixing-build-systems.md
+++ b/docs/markdown/Mixing-build-systems.md
@@ -12,7 +12,7 @@ is the common case.
 This page lists the Meson project's stance on mixing build systems.
 The tl/dr version is that while we do provide some functionality for
 this use case, it only works for simple cases. Anything more complex
-can not be made reliable and trying to do that would burden Meson
+cannot be made reliable and trying to do that would burden Meson
 developers with an effectively infinite maintenance burden. Thus these
 use cases are not guaranteed to work, and even if a project using them
 works today there are no guarantees that it will work in any future
diff --git a/docs/markdown/Release-notes-for-0.47.0.md b/docs/markdown/Release-notes-for-0.47.0.md
index f85a41b..c0e0fd7 100644
--- a/docs/markdown/Release-notes-for-0.47.0.md
+++ b/docs/markdown/Release-notes-for-0.47.0.md
@@ -24,7 +24,7 @@ preprocessor symbol's value `"ab" "cd"` is returned as `"abcd"`.
 Cross-compilation is now supported for ARM targets using ARM compiler
 version 6 - ARMCLANG. The required ARMCLANG compiler options for
 building a shareable library are not included in the current Meson
-implementation for ARMCLANG support, so it can not build shareable
+implementation for ARMCLANG support, so it cannot build shareable
 libraries. This current Meson implementation for ARMCLANG support can
 not build assembly files with arm syntax (we need to use armasm
 instead of ARMCLANG for the `.s` files with this syntax) and only
diff --git a/docs/markdown/Release-notes-for-0.49.0.md b/docs/markdown/Release-notes-for-0.49.0.md
index 6b84af1..4c09183 100644
--- a/docs/markdown/Release-notes-for-0.49.0.md
+++ b/docs/markdown/Release-notes-for-0.49.0.md
@@ -279,7 +279,7 @@ associated with the generated pkg-config file should be passed as
 first positional argument instead of in the `libraries` keyword
 argument. The previous behaviour is maintained but prints a
 deprecation warning and support for this will be removed in a future
-Meson release. If you can not create the needed pkg-config file
+Meson release. If you cannot create the needed pkg-config file
 without this warning, please file an issue with as much details as
 possible about the situation.
 
diff --git a/docs/markdown/Release-notes-for-0.51.0.md b/docs/markdown/Release-notes-for-0.51.0.md
index e015a95..da80db2 100644
--- a/docs/markdown/Release-notes-for-0.51.0.md
+++ b/docs/markdown/Release-notes-for-0.51.0.md
@@ -213,7 +213,7 @@ The output of `custom_target` and `custom_target[i]` can be used in
 integrating custom code generator steps, but note that there are many
 limitations:
 
- - Meson can not know about link dependencies of the custom target. If
+ - Meson cannot know about link dependencies of the custom target. If
    the target requires further link libraries, you need to add them manually
 
  - The user is responsible for ensuring that the code produced by
diff --git a/docs/markdown/Unit-tests.md b/docs/markdown/Unit-tests.md
index 664f99e..36fbdcf 100644
--- a/docs/markdown/Unit-tests.md
+++ b/docs/markdown/Unit-tests.md
@@ -61,7 +61,7 @@ your build directory.
 ## Parallelism
 
 To reduce test times, Meson will by default run multiple unit tests in
-parallel. It is common to have some tests which can not be run in
+parallel. It is common to have some tests which cannot be run in
 parallel because they require unique hold on some resource such as a
 file or a D-Bus name. You have to specify these tests with a keyword
 argument.
@@ -106,7 +106,7 @@ completed.
 
 ## Skipped tests and hard errors
 
-Sometimes a test can only determine at runtime that it can not be run.
+Sometimes a test can only determine at runtime that it cannot be run.
 
 For the default `exitcode` testing protocol, the GNU standard approach
 in this case is to exit the program with error code 77. Meson will