summaryrefslogtreecommitdiff
path: root/docs/runtime/stability.md
diff options
context:
space:
mode:
authorMatt Dumler <mattd3v@pm.me>2020-05-18 14:53:25 -0500
committerGitHub <noreply@github.com>2020-05-18 15:53:25 -0400
commit88b24261ba467c20d4ef90224b07c19a71398f0f (patch)
tree0c5b47c766208877adc3a2afb16506c888d6e50b /docs/runtime/stability.md
parent76ee5c780848a922dfc0ab8ac48096ab2262cc4a (diff)
adjust docs (#5598)
Diffstat (limited to 'docs/runtime/stability.md')
-rw-r--r--docs/runtime/stability.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/runtime/stability.md b/docs/runtime/stability.md
index cd7c27039..7fcc0f0b0 100644
--- a/docs/runtime/stability.md
+++ b/docs/runtime/stability.md
@@ -1,10 +1,10 @@
## Stability
-As of Deno 1.0.0, the `Deno` namespace APIs are stable. That means that we will
+As of Deno 1.0.0, the `Deno` namespace APIs are stable. That means we will
strive to make code working under 1.0.0 continue to work in future versions.
However, not all of Deno's features are ready for production yet. Features which
-are not ready because they are still in draft phase are locked behind the
+are not ready, because they are still in draft phase, are locked behind the
`--unstable` command line flag. Passing this flag does a few things:
- It enables the use of unstable APIs during runtime.
@@ -14,7 +14,7 @@ are not ready because they are still in draft phase are locked behind the
This includes the output of `deno types`.
You should be aware that unstable APIs have probably **not undergone a security
-review**, are likely to have **breaking API changes** in the future and are
+review**, are likely to have **breaking API changes** in the future, and are
**not ready for production**.
Furthermore Deno's standard modules (https://deno.land/std/) are not yet stable.