From 02d81338f9cae5f09491e21d314b85ce6c8d168a Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Fri, 19 Apr 2024 10:33:52 -0700 Subject: [PATCH] Update build-performance.mdx to fix some grammar --- pages/docs/manual/latest/build-performance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/manual/latest/build-performance.mdx b/pages/docs/manual/latest/build-performance.mdx index 93fb563e6..f1bf8e6c5 100644 --- a/pages/docs/manual/latest/build-performance.mdx +++ b/pages/docs/manual/latest/build-performance.mdx @@ -25,7 +25,7 @@ import Image from "src/components/Image"; ## Under the Hood -ReScript itself uses a build system under the hood, called [Ninja](https://ninja-build.org). Ninja is like Make, but cross-platform, minimal, focuses in perf and destined to be more of a low-level building block than a full-blown build system. In this regard, Ninja's a great implementation detail for `rescript`. +ReScript itself uses a build system under the hood, called [Ninja](https://ninja-build.org). Ninja is like Make, but cross-platform, minimal, focuses on perf and destined to be more of a low-level building block than a full-blown build system. In this regard, Ninja's a great implementation detail for `rescript`. ReScript reads into `rescript.json` and generates the Ninja build file in `lib/bs`. The file contains the low-level compiler commands, namespacing rules, intermediate artifacts generation & others. It then runs `ninja` for the actual build.