Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit dd1c94b

Browse files
authoredApr 8, 2025··
Make numbered list use only 1.
Addressing PR comment.
1 parent 54df433 commit dd1c94b

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed
 

Diff for: ‎src/about-this-guide.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -8,25 +8,25 @@ There are several parts to this guide:
88
1. [Building and debugging `rustc`][p1]:
99
Contains information that should be useful no matter how you are contributing,
1010
about building, debugging, profiling, etc.
11-
2. [Contributing to Rust][p2]:
11+
1. [Contributing to Rust][p2]:
1212
Contains information that should be useful no matter how you are contributing,
1313
about procedures for contribution, using git and Github, stabilizing features, etc.
14-
3. [Bootstrapping][p3]:
14+
1. [Bootstrapping][p3]:
1515
Describes how the Rust compiler builds itself using previous versions, including
1616
an introduction to the bootstrap process and debugging methods.
17-
4. [High-level Compiler Architecture][p4]:
17+
1. [High-level Compiler Architecture][p4]:
1818
Discusses the high-level architecture of the compiler and stages of the compile process.
19-
5. [Source Code Representation][p5]:
19+
1. [Source Code Representation][p5]:
2020
Describes the process of taking raw source code from the user
2121
and transforming it into various forms that the compiler can work with easily.
22-
6. [Supporting Infrastructure][p6]:
22+
1. [Supporting Infrastructure][p6]:
2323
Covers command-line argument conventions, compiler entry points like rustc_driver and
2424
rustc_interface, and the design and implementation of errors and lints.
25-
7. [Analysis][p7]:
25+
1. [Analysis][p7]:
2626
Discusses the analyses that the compiler uses to check various properties of the code
2727
and inform later stages of the compile process (e.g., type checking).
28-
8. [MIR to Binaries][p8]: How linked executable machine code is generated.
29-
9. [Appendices][p9] at the end with useful reference information.
28+
1. [MIR to Binaries][p8]: How linked executable machine code is generated.
29+
1. [Appendices][p9] at the end with useful reference information.
3030
There are a few of these with different information, including a glossary.
3131

3232
[p1]: ./building/how-to-build-and-run.html

0 commit comments

Comments
 (0)
Please sign in to comment.