Improve compatibility page, document '-c' flag

Author: Sainan

docs/Compatibility.md

@@ -3,7 +3,7 @@ sidebar_position: 10
 ---
 
 ## How compatible with Lua is Pluto?
-Pluto is 99.9% compatible with most Lua source code. However, it's imperfect. Due to that, Pluto implements several compatibility macros.
+Pluto is compatible with most Lua source code. However, it's imperfect. Due to that, Pluto has several compatibility options.
 ### Where are the incompatibilities?
 Pluto adds the following reserved tokens:
 - `switch`
@@ -18,13 +18,17 @@ Pluto adds the following reserved tokens:
 
 Which means you can't use them as variable names or for function calls. They can still be used with short-hand table indexes and goto labels though, because Pluto [removes the restriction from them](QoL%20Improvements/Reserved%20Identifiers).
 
-However, we have a simple solution for this: Compatibility Mode. This allows integrators to disable Pluto's reserved tokens. Integrators: Check your `luaconf.h` file to find the relevant macros under the "Compatibility" heading.
+### How to fix it?
+All of these incompatible keywords can be disabled:
+- **For Integrators:** Check your `luaconf.h` file to find the relevant macros under the "Compatibility" heading.
+- **For Scripters:** Place `-- @pluto_use * = false` at the top of the source file. [Read more...](#compile-time-configuration)
+- **For Users:** Pass the `-c` flag to `pluto` or `plutoc`.
 
-## Writing Scripts Under Compatibility Mode
-Obviously, you want to use Pluto's features, so how can you do it if the Pluto environment has all of its tokens disabled? The secret is that each reserved token mentioned above has a portable variant with a `pluto_` prefix. For example, `switch` has a twin called `pluto_switch` that is always valid.
+## For Scripters
+Because the Pluto environment your script is running in may have disabled some keywords for compatibility's sake, let's go over the portability and compatibility options given to you by Pluto.
 
 ### Compile-time Configuration
-You can also change the meaning of Pluto's reserved tokens at any point in your scripts using the `@pluto_use` annotation or `pluto_use` statement.
+You can change the meaning of Pluto's reserved tokens at any point in your scripts using the `@pluto_use` annotation or `pluto_use` statement.
 
 For example, to disable all non-compatible keywords except for `switch`:
 ```pluto
@@ -37,12 +41,14 @@ It is also possible to specify a version number, which is a shorthand for the ke
 - `"0.6.0"` corresponds to `* = false, switch, continue, enum, new, class, parent, export`
 - `"0.8.0"` corresponds to `* = false, switch, continue, enum, new, class, parent, export, try, catch`
 
-## Portability & proactive compatibility
-We recommend scripters use the `@pluto_use` annotation at the beginning of their scripts for two reasons:
+So, writing a portable script that makes use of Pluto 0.8.0's features simply requires this at the beginning:
+```pluto
+pluto_use "0.8.0"
+```
+
+We recommend you always place a `pluto_use` configuration at the beginning of your scripts for two reasons:
 - **Portability.** This will override the compatibility mode settings compiled into Pluto so your script will be parsed identically in all Pluto environments.
 - **Proactive compatibility.** Any keywords added by future versions of Pluto will also be put in compatibility mode by these statements, so in the off-chance your script uses a future reserved keyword as a variable name, it would still parse as you intended when you wrote it.
 
-Plus, it's as simple as this:
-```pluto
--- @pluto_use "0.8.0"
-```
+### Compatible Keywords
+Another way of using Pluto's features regardless of compatibility mode is by prefixing the keyword with `pluto_`. For example, `switch` becomes `pluto_switch`.

src/theme/pluto.js

@@ -1,6 +1,7 @@
 Prism.languages.pluto = {
 	'comment': /^#!.+|--(?:\[(=*)\[[\s\S]*?\]\1\]|.*)/m,
 	'attr-name': /(?<=(function|class|extends)\s)[\w:]+/,
+	'keyword': /\$|\b(?:and|as|class|pluto_class|enum|begin|break|do|else|elseif|end|for|function|goto|if|in|local|new|not|or|repeat|return|static|then|until|while|continue|switch|case|default|pluto_switch|pluto_continue|extends|export|pluto_export|pluto_use|public|private|try|catch|pluto_try|pluto_catch)\b/,
 	'function': [
 		/\b(?!in\s)(?!\d)(?!return)(?!case)(?!function)(?!local)(?!new)\w+(?=\s*(?:\??\())/, // func()
 		/\b(?!in\s)(?!\d)(?!return)(?!case)(?!function)(?!local)(?!not)\w+(?=\s*(?:\??[{"]))/, // func "", func {}
@@ -17,7 +18,6 @@ Prism.languages.pluto = {
 	},
 	'boolean': /\b(?:true|false)\b/,
 	'number': /\b([\d][\d_]+|(0x[a-f\d]+)|(0b[01]+))(?:\.[a-f\d]*)?(?:p[+-]?\d+)?\b|\b\d+(?:\.\B|(?:\.\d*)?(?:e[+-]?\d+)?\b)|\B\.\d+(?:e[+-]?\d+)?\b/i,
-	'keyword': /\$|\b(?:and|as|class|pluto_class|enum|begin|break|do|else|elseif|end|for|function|goto|if|in|local|new|not|or|repeat|return|static|then|until|while|continue|switch|case|default|pluto_switch|pluto_continue|extends|export|pluto_export|pluto_use|public|private|try|catch|pluto_try|pluto_catch)\b/,
 	'variable': /\b(?:self|parent|pluto_parent)\b/,
 	'operator': [
 		/[-+*%^&|#]|\/\/?|<[<=]?|>[>=]?|[=~]=?|\:=|\?|(?<!\w)\:|\?\.|instanceof/,