diff options
| -rw-r--r-- | bench/hot-module-reloading/css-stress-test/README.md | 2 | ||||
| -rw-r--r-- | docs/bun-flavored-toml.md | 2 | ||||
| -rw-r--r-- | packages/bun-macro-relay/README.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/bench/hot-module-reloading/css-stress-test/README.md b/bench/hot-module-reloading/css-stress-test/README.md index 0d373de5e..b77a2b455 100644 --- a/bench/hot-module-reloading/css-stress-test/README.md +++ b/bench/hot-module-reloading/css-stress-test/README.md @@ -36,7 +36,7 @@ bun is 14x faster than Next.js at hot reloading CSS. It times pixels instead of builds. `color-looper.zig` writes color updates and the timestamp to a css file, while simultaneously screen recording a non-headless Chromium instance. After it finishes, it OCRs the video frames and verifies the scanned timestamps against the actual data. This data measures (1) how long each update took from saving to disk up to the pixels visible on the screen and (2) what % of frames were rendered. -The intent is to be as accurate as possible. Measuring times reported client-side is simpler, but lower accuracy since those times may not correspond to pixels on the screen and do not start from when the data was written to disk (at best, they measure when the filesystem watcher detected the update, but often not that either). `color-looper.zig` must run separately from `browser.js` or the results will be innaccurate. +The intent is to be as accurate as possible. Measuring times reported client-side is simpler, but lower accuracy since those times may not correspond to pixels on the screen and do not start from when the data was written to disk (at best, they measure when the filesystem watcher detected the update, but often not that either). `color-looper.zig` must run separately from `browser.js` or the results will be inaccurate. It works like this: diff --git a/docs/bun-flavored-toml.md b/docs/bun-flavored-toml.md index 1a7587470..b041ba055 100644 --- a/docs/bun-flavored-toml.md +++ b/docs/bun-flavored-toml.md @@ -2,7 +2,7 @@ [TOML](https://toml.io/) is a minimal configuration file format designed to be easy for humans to read. -Bun implements a TOML parser with a few tweaks designed for better interopability with INI files and with JavaScript. +Bun implements a TOML parser with a few tweaks designed for better interoperability with INI files and with JavaScript. ### ; and # are comments diff --git a/packages/bun-macro-relay/README.md b/packages/bun-macro-relay/README.md index 6afb16852..157163af5 100644 --- a/packages/bun-macro-relay/README.md +++ b/packages/bun-macro-relay/README.md @@ -1,6 +1,6 @@ # bun-macro-relay -This lets you use Faceook's [Relay](https://github.com/facebook/relay) framework (GraphQL) with bun. +This lets you use Facebook's [Relay](https://github.com/facebook/relay) framework (GraphQL) with bun. Specifically, this implements the bun equivalent of [`babel-plugin-relay`](https://github.com/facebook/relay/tree/main/packages/babel-plugin-relay). It parses `graphql` queries, but does not compile/save them to your artifacts directory, you still need [`relay-compiler`](https://github.com/facebook/relay/tree/main/packages/relay-compiler) for that. |