diff --git a/utils/website/graphile-export/how-it-works.md b/utils/website/graphile-export/how-it-works.md
index 6e853c160..ae339574b 100644
--- a/utils/website/graphile-export/how-it-works.md
+++ b/utils/website/graphile-export/how-it-works.md
@@ -63,7 +63,7 @@ code out, and now it can see the value of that "invisible" `a=7`:
 [ 7 ]
 ```
 
-Thus everything that can have these kinds of hidden properties must be wrapped
+Thus everything that can reference values from a parent scope must be wrapped
 in an `EXPORTABLE` call. Sometimes the inputs to the `EXPORTABLE` call
 themselves also have to be wrapped in an `EXPORTABLE` call. You'll figure out
 which things need wrapping by looking at the exported code and seeing where
diff --git a/utils/website/graphile-export/index.md b/utils/website/graphile-export/index.md
index 733e83969..703511ac1 100644
--- a/utils/website/graphile-export/index.md
+++ b/utils/website/graphile-export/index.md
@@ -11,8 +11,8 @@ The key reason to export your schema is to move schema introspection of postgres
 from runtime to build time. This results in:
 
 - Faster startup time
-- Reduced thundering herd on the database in the event of an outage
-- Much faster cold starts for Lambda
+- Reduced thundering herd in the event of mass server restarts
+- Much faster cold starts for serverless environments such as AWS Lambda
 - And probably more
 
 Previously, in Postgraphile 4, export took the form of encoding the Postgres