Skip to content

Commit 5be62ee

Browse files
authored
Carify dependency direction in link doc (#1130)
'linking' is something of a symmetric verb. Linking packages A and B doesn't imply a specific hierarchy. Replacing one instance of *link* here with *consume* make the direction of the dependency more obvious on first read.
1 parent 3e7854d commit 5be62ee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

lang/en/docs/cli/link.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ There are two commands to facilitate this workflow:
1616

1717
##### `yarn link` (in package you want to link) <a class="toc" id="toc-yarn-link-in-package-you-want-to-link" href="#toc-yarn-link-in-package-you-want-to-link"></a>
1818

19-
This command is run in the package folder you'd like to link. For example if you
19+
This command is run in the package folder you'd like to consume. For example if you
2020
are working on `react` and would like to use your local version to debug a
2121
problem in `react-relay`, simply run `yarn link` inside of the `react` project.
2222

0 commit comments

Comments
 (0)