diff --git a/packages/docs/docs/guides/esm.md b/packages/docs/docs/guides/esm.md
index c81cc0615..bcb74d9d3 100644
--- a/packages/docs/docs/guides/esm.md
+++ b/packages/docs/docs/guides/esm.md
@@ -1,6 +1,6 @@
 # ESM
 
-AI.JSX exports both CJS and ESM files. When you `import` or `require` `ai-jsx`, you'll get the file that matches the module system you're using. If you have a problem with this, please let us know.
+AI.JSX exports both CJS and ESM files. When you `import` or `require` `ai-jsx`, you'll get the file that matches the module system you're using. If you have a problem with this, please let us know by either [dropping us a line in Discord](https://discord.com/invite/MsKAeKF8kU) or by [opening an issue](https://github.com/fixie-ai/ai-jsx/issues) on GitHub.
 
 ## Known Issues
 
@@ -16,7 +16,7 @@ However, when you run `tsc`, you don't get an error.
 
 When VS Code and `tsc` give contradictory results, it may mean that VS Code's magic for finding your `tsconfig` isn't working. This can happen if your `tsconfig` is in an unusual place or has an unusual name.
 
-To resolve it, put a `tsconfig.json` somewhere the VS Code will find it – probably the root of your package. If you have a reason that you want your `tsconfig.json` to live elsewhere, you can make your newly-added `tsconfig.json` just a proxy to the real one:
+To resolve it, put a `tsconfig.json` somewhere that VS Code will find it – probably the root of your package. If you have a reason that you want your `tsconfig.json` to live elsewhere, you can make your newly-added `tsconfig.json` just a proxy to the real one:
 
 ```json
 {