summaryrefslogtreecommitdiff
path: root/docs/markdown/Cross-compilation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/markdown/Cross-compilation.md')
-rw-r--r--docs/markdown/Cross-compilation.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/markdown/Cross-compilation.md b/docs/markdown/Cross-compilation.md
index 0cfef71b9..64196f3bd 100644
--- a/docs/markdown/Cross-compilation.md
+++ b/docs/markdown/Cross-compilation.md
@@ -85,7 +85,7 @@ their user interface much more complex.
The most complicated case is when you cross-compile a cross compiler.
As an example you can, on a Linux machine, generate a cross compiler
-that runs on Windows but produces binaries on MIPS Linux. In this case
+that runs on Windows but produces binaries for MIPS Linux. In this case
*build machine* is x86 Linux, *host machine* is x86 Windows and
*target machine* is MIPS Linux. This setup is known as the [Canadian
Cross](https://en.wikipedia.org/wiki/Cross_compiler#Canadian_Cross).