Skip to content

Commit 6e75c27

Browse files
committed
Address linter
1 parent 5b34641 commit 6e75c27

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

.github/linters/.markdown-lint.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,5 +2,5 @@ default: true
22
MD013: # line length
33
code_block_line_length: 256
44
heading_line_length: 96
5-
line_length: 96
5+
line_length: 256
66
MD033: false # no inline HTML

Documentation/how-to-stage2-build.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This document describes how to perform a stage 2 source build.
44

55
## What is a stage 2 build
66

7-
A **stage 2 build** is when you run a source build, then take the SDK and packages produced by that build and use them to rebuild the product.
7+
A **stage 2 build** is when you run a source build, then take the SDK and packages produced by that build and use them to rebuild the product.
88
Stage 2 builds are essential for validating a source‑built product.
99

1010
It’s common for stage 2 builds to surface issues.
@@ -14,7 +14,6 @@ These issues must be resolved for the product to be considered **source‑builda
1414
The process of using built SDK and artifacts to rebuild the product is often called **bootstrapping**.
1515
Distribution maintainers use it to initiate the build process: build once using the Microsoft SDK and artifacts, then rebuild using the resulting SDK and artifacts.
1616

17-
1817
## Steps to run a stage 2 build
1918

2019
1. Run a stage 1 build

0 commit comments

Comments
 (0)