From 2d18eff544093882d45b7e1e97a0876247324f2b Mon Sep 17 00:00:00 2001 From: Liu Yuxi Date: Sun, 17 Mar 2024 19:23:21 +0100 Subject: [PATCH] doc: lake: fix typo (#3704) Closes #3703 --- src/lake/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lake/README.md b/src/lake/README.md index f035f2e0ff..b4f8988bd1 100644 --- a/src/lake/README.md +++ b/src/lake/README.md @@ -141,7 +141,7 @@ Lake uses a lot of terms common in software development -- like workspace, packa * A **facet** is an element built from another organizational unit (e.g., a package, module, library, etc.). For instance, Lake produces `olean`, `ilean`, `c`, and `o` files all from a single module. Each of these components are thus termed a *facet* of the module. Similarly, Lake can build both static and shared binaries from a library. Thus, libraries have both `static` and `shared` facets. Lake also allows users to define their own custom facets to build from modules and packages, but this feature is currently experimental and not yet documented. -* A **trace** is a piece of data (generally a hash) which is used to verify whether a given target is up-to-date (i.e., does not not need to be rebuilt). If the trace stored with a built target matches the trace computed during build, then a target is considered up-to-date. A target's trace is derived from its various **inputs** (e.g., source file, Lean toolchain, imports, etc.). +* A **trace** is a piece of data (generally a hash) which is used to verify whether a given target is up-to-date (i.e., does not need to be rebuilt). If the trace stored with a built target matches the trace computed during build, then a target is considered up-to-date. A target's trace is derived from its various **inputs** (e.g., source file, Lean toolchain, imports, etc.). ## Package Configuration Options