about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2019-11-07 22:10:49 +0200
committerWho? Me?! <mark-i-m@users.noreply.github.com>2019-11-08 10:19:32 -0600
commiteb26cd56ca8b27a76d3652d9e007b27b6726169e (patch)
tree9a06bef13ba7e83c065671bdf3489e75efa68ee0 /src/doc/rustc-dev-guide
parentc314450b99e55852d3f40f7f7f30dd25ce283125 (diff)
downloadrust-eb26cd56ca8b27a76d3652d9e007b27b6726169e.tar.gz
rust-eb26cd56ca8b27a76d3652d9e007b27b6726169e.zip
whitespace
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/building/compiler-documenting.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/doc/rustc-dev-guide/src/building/compiler-documenting.md b/src/doc/rustc-dev-guide/src/building/compiler-documenting.md
index 5c80c3d1c85..345a324bd7c 100644
--- a/src/doc/rustc-dev-guide/src/building/compiler-documenting.md
+++ b/src/doc/rustc-dev-guide/src/building/compiler-documenting.md
@@ -2,10 +2,10 @@
 
 You might want to build documentation of the various components
 available like the standard library. There’s two ways to go about this.
- You can run rustdoc directly on the file to make sure the HTML is
- correct, which is fast. Alternatively, you can build the documentation
- as part of the  build process through x.py. Both are viable methods
- since documentation  is more about the content.
+You can run rustdoc directly on the file to make sure the HTML is
+correct, which is fast. Alternatively, you can build the documentation
+as part of the build process through x.py. Both are viable methods
+since documentation is more about the content.
 
 ## Document everything