summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCasey Rodarmor <casey@rodarmor.com>2023-12-24 03:34:51 +0800
committerGitHub <noreply@github.com>2023-12-23 19:34:51 +0000
commit660ae2137397612d3e44a8e83ae5af32e2b64ff0 (patch)
tree9d5bdd26acde7af95c505b43619556d180951675
parente9bec8d398cd8a561185cf6336fcffd0d15d31e9 (diff)
Tweak readme (#1775)
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index d7865b1f..2eea7fed 100644
--- a/README.md
+++ b/README.md
@@ -2743,7 +2743,7 @@ On a big project with multiple contributors, it's very useful to have a file wit
There are probably different commands to test, build, lint, deploy, and the like, and having them all in one place is useful and cuts down on the time you have to spend telling people which commands to run and how to type them.
-And, with an easy place to put commands, it's likely that you'll come up with other useful things which are part of the project's collective wisdom, but which aren't written down anywhere, like the arcane commands needed for some part of your revision control workflow, install all your project's dependencies, or all the random flags you might need to pass to the build system.
+And, with an easy place to put commands, it's likely that you'll come up with other useful things which are part of the project's collective wisdom, but which aren't written down anywhere, like the arcane commands needed for some part of your revision control workflow, to install all your project's dependencies, or all the random flags you might need to pass to the build system.
Some ideas for recipes: