From 7652bda7d5ba4bdcdc03b85ffbd5467ca7f504b2 Mon Sep 17 00:00:00 2001 From: "LamTrinh.Dev" Date: Tue, 20 Aug 2024 19:36:59 +0700 Subject: [PATCH] [docs] Fix typo issue at Foundation_Build_Process.md --- Foundation_Build_Process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Foundation_Build_Process.md b/Foundation_Build_Process.md index fb04bff89..a18f8ccc4 100644 --- a/Foundation_Build_Process.md +++ b/Foundation_Build_Process.md @@ -16,7 +16,7 @@ This is the quickest way to iterate on Foundation to add new APIs or fix bugs. S ## Individual Build (via SwiftPM) -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. +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. ### When is this configuration used? @@ -129,4 +129,4 @@ An installation guide can be found in the [Getting Started article](https://swif Afterwards you can run the benchmarks from CLI by going to the `Benchmarks` subfolder (e.g. `cd Benchmarks`) and invoking: ``` swift package benchmark -``` \ No newline at end of file +```