Adjusted docs text

Author: Perryvw

docs/caveats.md

@@ -2,7 +2,7 @@
 title: Caveats
 ---
 
-Luckily, for most use-cases, you can write modern, idiomatic TypeScript, and TSTL will produce transpiled Lua that will work flawlessly. In other words, you probably will not have to worry about the idiomatic quirks of Lua or the internal decisions that TSTL makes when converting code.
+TSTL aims to support almost all modern, idiomatic TypeScript without any modifications. In other words, you probably will not have to worry about the idiomatic quirks of Lua or other internal decisions that TSTL makes when converting code.
 
 With that said, TSTL does have some "gotchas" that you might run into. This page covers some of those edge-cases.
 
@@ -21,7 +21,7 @@ With that said, TSTL does have some "gotchas" that you might run into. This page
 
 ## Differences from JavaScript
 
-This project aims for both compilation results to have the same behavior as much as possible, but not at all costs. Since TypeScript is based on JavaScript, it also inherited some of the quirks in JavaScript that are not present in Lua. This is where behavior between Lua and JavaScript compilation targets diverge. TypeScriptToLua aims to keep identical behavior as long as **sane** TypeScript is used: if JavaScript-specific quirks are used, behavior might differ.
+This project aims for JavaScript and Lua compilation results to have the same runtime behavior as much as possible, but not at all costs. Since TypeScript is based on JavaScript, it also inherited some of the quirks in JavaScript that are not present in Lua. This is where behavior between Lua and JavaScript compilation targets diverge. TypeScriptToLua aims to keep identical behavior as long as **sane** TypeScript is used: if JavaScript-specific quirks are used, behavior might differ.
 
 Below are some of the cases where resulting Lua intentionally behaves different from compiled JS.
 
@@ -118,7 +118,7 @@ A sorting algorithm is [said to be stable](https://stackoverflow.com/questions/1
 
 TypeScriptToLua relies on the Lua standard library for sorting. In other words, it transpiles `[1, 2, 3].sort();` to `table.sort({1, 2, 3})`. So beware that your sorts will no longer be stable!
 
-If you need stable sorting, you have to manually use a custom sorting function. For some examples of this, see the [sorting helper functions from `isaacscript-common`](https://github.com/IsaacScript/isaacscript/blob/main/packages/isaacscript-common/src/functions/sort.ts).
+If you need stable sorting, you will have to implement your own sorting algorithm or find a library that provides one.
 
 ### Local Variable Limit
 

docs/external-code.md

@@ -2,7 +2,7 @@
 title: External Code
 ---
 
-In your `tstl` project, you might want to import some existing Lua code. Or, you might want to import a library from [npm](https://www.npmjs.com/). This page describes how to use external code.
+In your `tstl` project, you might want to use some existing Lua code. Or you might want to import a Lua library from [npm](https://www.npmjs.com/). This page describes how to use external Lua with your TypeScript code and TSTL.
 
 :::note
 This page is about importing code that **actually executes something**. In a `tstl` project, it is common to depend on external library that provide type declarations. Type declaration libraries only provide types: they do not contribute any code to your actual program output. Thus, they work a little differently from what is discussed on this page. For information on how type declarations work, see the [type declarations page](advanced/writing-declarations.md).

docs/getting-started.md

@@ -11,14 +11,7 @@ Note that we assume that you are already familiar with how TypeScript works. If
 TypeScriptToLua is built using [Node.js](https://nodejs.org/) and distributed via [npm](https://www.npmjs.com/). To install it, you need to create a `package.json` file in the root of your project, containing at least `{}`. Then, you can add the latest version of TypeScriptToLua to your project:
 
 ```bash
-# If you use npm:
-npm install --save-dev typescript-to-lua
-
-# If you use yarn:
-yarn add --dev typescript-to-lua
-
-# If you use pnpm:
-pnpm add --save-dev typescript-to-lua
+npm install --save-dev typescript-to-lua typescript
 ```
 
 (If you don't know the difference between the package managers, choose `npm`.)
@@ -49,39 +42,22 @@ TypeScriptToLua is configured using a `tsconfig.json` file. (This is the same fi
 }
 ```
 
-If your target Lua environment is not [LuaJIT](https://luajit.org/), make sure to change the value of `luaTarget`. Valid values are `JIT`, `5.3`, `5.2`, `5.1`, `5.0`, and `universal`.
+Make sure to set the value of `luaTarget` to the Lua version of your environment. Valid values are `JIT`, `5.4`, `5.3`, `5.2`, `5.1`, `5.0`, and `universal`.
 
 :::note
 You can find out the version of your Lua environment by running: `print(_VERSION)`
 :::
 
 Check out [configuration page](configuration.md) for more information.
 
-### Strictest Configuration
-
-If you want the TypeScript compiler to be as strict as possible, then you need to enable some additional flags. Handily, we can extend from [the "strictest" TypeScript community config](https://github.com/tsconfig/bases/blob/main/bases/strictest.json) to abstract this away by adding this to top of the `tsconfig.json` file:
-
-```json
-  // We extend the strictest base config:
-  // https://github.com/tsconfig/bases/blob/main/bases/strictest.json
-  "extends": "@tsconfig/strictest/tsconfig.json",
-```
-
 ## Building your project
 
 Our command line interface is called `tstl` and it works almost exactly the same as TypeScript's `tsc`.
 
 Since `tstl` is installed locally to your project, you cannot run it as a bare command in your terminal. Instead, use:
 
 ```bash
-# If you use npm:
-npx tstl
-
-# If you use yarn (yarn also uses npx):
 npx tstl
-
-# If you use pnpm:
-pnpm exec tstl
 ```
 
 :::note

docs/publishing-modules.md

@@ -61,7 +61,6 @@ Note that:
 
 When you are ready to publish:
 
-- Use `npm login` to cache your npm credentials.
 - Use `npm publish --dry-run` to see what files would be published without actually uploading anything.
 - Use `npm publish` to actually upload it.
 

package.json

@@ -3,7 +3,6 @@
     "scripts": {
         "start": "docusaurus start",
         "build": "docusaurus build",
-        "serve": "docusaurus serve",
         "lint": "npm run lint:prettier",
         "lint:prettier": "prettier --check .",
         "fix:prettier": "prettier --write .",

sidebars.json

@@ -8,6 +8,7 @@
                 "configuration",
                 "caveats",
                 "the-self-parameter",
+                "advanced/writing-declarations",
                 "external-code",
                 "publishing-modules",
                 "editor-support"
@@ -16,13 +17,7 @@
         {
             "type": "category",
             "label": "Advanced",
-            "items": [
-                "advanced/writing-declarations",
-                "advanced/compiler-annotations",
-                "advanced/language-extensions",
-                "json-modules",
-                "jsx"
-            ]
+            "items": ["advanced/language-extensions", "json-modules", "jsx", "advanced/compiler-annotations"]
         },
         {
             "type": "category",