From 6e0b8c6f2de357ef81ff97e81abf51d26ca13dc4 Mon Sep 17 00:00:00 2001 From: Jorge Celaya Date: Wed, 20 Nov 2024 17:13:34 -0600 Subject: [PATCH] docs(turbopack): fix typo in incremental-computation page --- docs/pack-docs/incremental-computation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pack-docs/incremental-computation.mdx b/docs/pack-docs/incremental-computation.mdx index b40f14f9d1aac..58d225fde9f96 100644 --- a/docs/pack-docs/incremental-computation.mdx +++ b/docs/pack-docs/incremental-computation.mdx @@ -37,7 +37,7 @@ Many build systems include explicit dependency graphs that must be manually popu The difficulty of specifying an explicit dependency graph means that usually caching is done at a coarse file-level granularity. This granularity does have some benefits: less incremental results means less data to cache, which might be worth it if you have limited disk space or memory. -An example of such an architecture is [GNU Make](https://www.gnu.org/software/make/), where output targets and prerequisites are manually configured and represented as files. Systems like GNU Make miss caching opportunities due to their coarse granularity: they does not understand and cannot cache internal data structures within the compiler. +An example of such an architecture is [GNU Make](https://www.gnu.org/software/make/), where output targets and prerequisites are manually configured and represented as files. Systems like GNU Make miss caching opportunities due to their coarse granularity: they do not understand and cannot cache internal data structures within the compiler. ## Function-level fine-grained automatic incremental computation