summaryrefslogtreecommitdiff
path: root/docs/npm.md
diff options
context:
space:
mode:
authorDidier Durand <[email protected]>2025-07-05 17:23:39 +0200
committerGitHub <[email protected]>2025-07-05 15:23:39 +0000
commitab96676e360b57cb5467826793288d4d6e003d60 (patch)
tree2367b013462ed831cc436b1b1632915c0aaf6e2b /docs/npm.md
parent47dc16d243d7a7fb82f52ad5028d2c0692b8e333 (diff)
fix typos in diverse files (#3284)
Co-authored-by: Scott Densmore <[email protected]>
Diffstat (limited to 'docs/npm.md')
-rw-r--r--docs/npm.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/npm.md b/docs/npm.md
index 01b99ccd..e39debc1 100644
--- a/docs/npm.md
+++ b/docs/npm.md
@@ -20,7 +20,7 @@ This project follows a structured release process to ensure that all packages ar
## Current Theory
-For most all changes, simply patching the minor version is acceptable. We can and should release frequently; the more often we release the easier it is to tell what change broke something. Developeres are encouraged to push a release as described below after their branch merges. I also think I'm open to doing the release publishing steps as a part of an existing PR, though this could have more churn if others are also releasing and version numbers change frequently.
+For most all changes, simply patching the minor version is acceptable. We can and should release frequently; the more often we release the easier it is to tell what change broke something. Developers are encouraged to push a release as described below after their branch merges. I also think I'm open to doing the release publishing steps as a part of an existing PR, though this could have more churn if others are also releasing and version numbers change frequently.
## How To Release