Skip to content

Commit 7b74cf0

Browse files
committed
Update pinned-dependency doc wording
1 parent 023dd90 commit 7b74cf0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

pages/docs/manual/latest/build-pinned-dependencies.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ canonical: "/docs/manual/latest/build-pinned-dependencies"
99

1010
**Since 8.4**
1111

12-
Usually we'd recommend to use ReScript in a single-codebase style: One `bsconfig.json` file for the whole codebase.
12+
Usually we'd recommend to use ReScript in a single-codebase style by using one `bsconfig.json` file for your whole codebase.
1313

14-
There are scenarios where you still want to connect and build multiple independent ReScript packages for one main project though. This is where `pinned-dependencies` come into play.
14+
There are scenarios where you still want to connect and build multiple independent ReScript packages for one main project though (`yarn workspaces`-like "monorepos"). This is where `pinned-dependencies` come into play.
1515

1616

1717
## Package Types
@@ -49,7 +49,7 @@ The build system respects the following rules for each package type:
4949
- Ignores pinned dependencies
5050
- Ignores custom generator rules
5151

52-
So with that knowledge in mind, let's dive into some more concrete examples to see our `pinned dependencies` in action.
52+
So with that knowledge in mind, let's dive into some more concrete examples to see our pinned dependencies in action.
5353

5454
## Examples
5555

0 commit comments

Comments
 (0)