Skip to content

Commit 8d8920e

Browse files
authored
[docs] Fix typo issue at Foundation_Build_Process.md (#876)
1 parent fd4788a commit 8d8920e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Foundation_Build_Process.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This is the quickest way to iterate on Foundation to add new APIs or fix bugs. S
1616

1717
## Individual Build (via SwiftPM)
1818

19-
Each invididual project can be built via SwiftPM. This is useful when quickly iterating at desk and when developing within IDEs with integrated SwiftPM support such as Xcode. The SwiftPM build is configured via the `Package.swift` manifest at the root directory of each project. This build format supports building only Foundation components and their immediate dependencies without the need to build other toolchain libraries such as the standard library or the compiler itself. This is also the only build format that supports building and running unit tests.
19+
Each individual project can be built via SwiftPM. This is useful when quickly iterating at desk and when developing within IDEs with integrated SwiftPM support such as Xcode. The SwiftPM build is configured via the `Package.swift` manifest at the root directory of each project. This build format supports building only Foundation components and their immediate dependencies without the need to build other toolchain libraries such as the standard library or the compiler itself. This is also the only build format that supports building and running unit tests.
2020

2121
### When is this configuration used?
2222

@@ -129,4 +129,4 @@ An installation guide can be found in the [Getting Started article](https://swif
129129
Afterwards you can run the benchmarks from CLI by going to the `Benchmarks` subfolder (e.g. `cd Benchmarks`) and invoking:
130130
```
131131
swift package benchmark
132-
```
132+
```

0 commit comments

Comments
 (0)