Skip to content

Commit 576581d

Browse files
committed
fix some more typos
1 parent 8cbf9d0 commit 576581d

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/how-to-build-and-run.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -209,13 +209,14 @@ The sequence of commands you want is as follows:
209209
- Subsequent builds: `./x.py build -i --stage 1 src/libstd --keep-stage 1`
210210
- Note that we added the `--keep-stage 1` flag here
211211

212-
The effect of `--keep-stage1` is that we just *assume* that the old
212+
The effect of `--keep-stage 1` is that we just *assume* that the old
213213
standard library can be re-used. If you are editing the compiler, this
214214
is almost always true: you haven't changed the standard library, after
215215
all. But sometimes, it's not true: for example, if you are editing
216216
the "metadata" part of the compiler, which controls how the compiler
217-
encodes types and other states into the `rlib` files, or if you are editing
218-
things that wind up in the metadata (such as the definition of the MIR).
217+
encodes types and other states into the `rlib` files, or if you are
218+
editing things that wind up in the metadata (such as the definition of
219+
the MIR).
219220

220221
**The TL;DR is that you might get weird behavior from a compile when
221222
using `--keep-stage 1`** -- for example, strange [ICEs](appendix/glossary.html) or other

0 commit comments

Comments
 (0)