From 4143d989812a585aa09ef4be2ff16fd93370da58 Mon Sep 17 00:00:00 2001 From: John Spurlock Date: Thu, 1 Apr 2021 04:19:45 -0500 Subject: [PATCH] Fix typo in faqs.md (#9948) Co-authored-by: Kitson Kelly --- docs/typescript/faqs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/typescript/faqs.md b/docs/typescript/faqs.md index 338537fc8b..65f1d92b7d 100644 --- a/docs/typescript/faqs.md +++ b/docs/typescript/faqs.md @@ -6,9 +6,9 @@ Maybe. That is the best answer, we are afraid. For lots of reasons, Deno has chosen to have fully qualified module specifiers. In part this is because it treats TypeScript as a first class language. Also, Deno uses explicit module resolution, with no _magic_. This is effectively the same way browsers -themselves work, thought they don't obviously support TypeScript directly. If -the TypeScript modules use imports that don't have these design decisions in -mind, they may not work under Deno. +themselves work, though they don't obviously support TypeScript directly. If the +TypeScript modules use imports that don't have these design decisions in mind, +they may not work under Deno. Also, in recent versions of Deno (starting with 1.5), we have started to use a Rust library to do transformations of TypeScript to JavaScript in certain