diff options
| author |  0xflotus <0xflotus@gmail.com>
| 2023-07-29 12:58:45 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2023-07-29 03:58:45 -0700 |
| commit | dccf82b1c682a84c42540ba9e00e5e9296cc7e5f (patch) | |
| tree | 18778b43288415fb057049992c7d2d914bbc31ee | |
| parent | 5563be99d33d02f2e7ddc1c3fadcb0cffeee72d8 (diff) | |
| download | bun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.tar.gz bun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.tar.zst bun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.zip | |
docs: fixed small errors (#3879)
* Update cache.md
* Update index.md
* Update macros.md
* Update writing.md
| -rw-r--r-- | docs/bundler/index.md | 2 | ||||
| -rw-r--r-- | docs/bundler/macros.md | 2 | ||||
| -rw-r--r-- | docs/install/cache.md | 2 | ||||
| -rw-r--r-- | docs/test/writing.md | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/docs/bundler/index.md b/docs/bundler/index.md index da1c3ecae..bfbed2077 100644 --- a/docs/bundler/index.md +++ b/docs/bundler/index.md @@ -482,7 +482,7 @@ n/a {% /codetabs %} -Bun implements a univeral plugin system for both Bun's runtime and bundler. Refer to the [plugin documentation](/docs/bundler/plugins) for complete documentation. +Bun implements a universal plugin system for both Bun's runtime and bundler. Refer to the [plugin documentation](/docs/bundler/plugins) for complete documentation. <!-- ### `manifest` diff --git a/docs/bundler/macros.md b/docs/bundler/macros.md index 729f8350b..ecba16c0d 100644 --- a/docs/bundler/macros.md +++ b/docs/bundler/macros.md @@ -33,7 +33,7 @@ As you can see, the source code of the `random` function occurs nowhere in the b ## When to use macros -If you have several build scripts for small things where you would otherwise have a one-off build script, bundle-time code execution can be easier to maintain. It lives with the rest of your code, it runs with the rest of the build, it is automatically paralellized, and if it fails, the build fails too. +If you have several build scripts for small things where you would otherwise have a one-off build script, bundle-time code execution can be easier to maintain. It lives with the rest of your code, it runs with the rest of the build, it is automatically parallelized, and if it fails, the build fails too. If you find yourself running a lot of code at bundle-time though, consider running a server instead. diff --git a/docs/install/cache.md b/docs/install/cache.md index 6bd13d04a..bb22e545d 100644 --- a/docs/install/cache.md +++ b/docs/install/cache.md @@ -19,7 +19,7 @@ disableManifest = false ## Minimizing re-downloads -Bun strives to avoid re-downloading packages mutiple times. When installing a package, if the cache already contains a version in the range specified by `package.json`, Bun will use the cached package instead of downloading it again. +Bun strives to avoid re-downloading packages multiple times. When installing a package, if the cache already contains a version in the range specified by `package.json`, Bun will use the cached package instead of downloading it again. {% details summary="Installation details" %} If the semver version has pre-release suffix (`1.0.0-beta.0`) or a build suffix (`1.0.0+20220101`), it is replaced with a hash of that value instead, to reduce the chances of errors associated with long file paths. diff --git a/docs/test/writing.md b/docs/test/writing.md index e5e3fe1b0..a99af8b90 100644 --- a/docs/test/writing.md +++ b/docs/test/writing.md @@ -101,7 +101,7 @@ test.todo("fix this", () => { }); ``` -To exlusively run tests marked as _todo_, use `bun test --todo`. +To exclusively run tests marked as _todo_, use `bun test --todo`. ```sh $ bun test --todo |