v3.0

assets/jsconfig.json

@@ -0,0 +1,10 @@
+{
+ "compilerOptions": {
+  "baseUrl": ".",
+  "paths": {
+   "*": [
+    "../node_modules/mermaid/*"
+   ]
+  }
+ }
+}

config/postcss.config.js

@@ -22,6 +22,7 @@ module.exports = {
         'alert-link',
         'container-xxl',
         'container-fluid',
+        'container-fw ',
         ...whitelister([
           './assets/scss/components/_alerts.scss',
           './assets/scss/components/_buttons.scss',
@@ -32,6 +33,9 @@ module.exports = {
           './assets/scss/common/_dark.scss',
           './node_modules/bootstrap/scss/_dropdown.scss',
           './node_modules/katex/dist/katex.css',
+          './node_modules/@hyas/doks-core/assets/scss/components/_code.scss',
+          './node_modules/@hyas/doks-core/assets/scss/components/_expressive-code.scss',
+          './node_modules/@hyas/doks-core/assets/scss/common/_syntax.scss',
         ]),
       ],
     }),

content/en/docs/topics/config/index.md

@@ -52,6 +52,17 @@ StylesPath = "ci/vale/styles"
 (e.g., styles and ignore files\). The path value may be absolute or relative to
 the location of the parent `.vale.ini` file.
 
+As of v3.0.0, Vale supports a default `StylesPath`. The location of this path
+depends on your operating system:
+
+| OS      | Search Locations                                     |
+| :------ | :--------------------------------------------------- |
+| Windows | `%LOCALAPPDATA%\vale\styles`                         |
+| macOS   | `$HOME/Library/Application Support/vale/styles`      |
+| Unix    | `$XDG_DATA_HOME/vale/styles`                         |
+
+(Run the `vale ls-dirs` command to see the exact locations on your system.)
+
 #### MinAlertLevel
 
 ```ini
@@ -296,9 +307,11 @@ configuration depends on your operating system:
 
 | OS      | Search Locations                                     |
 | :------ | :--------------------------------------------------- |
-| Windows | `%AppData%\vale`                                     |
-| macOS   | `$HOME/Library/Application Support/vale`             |
-| Unix    | `$XDG_CONFIG_HOME/vale`                              |
+| Windows | `%LOCALAPPDATA%\vale\.vale.ini`                      |
+| macOS   | `$HOME/Library/Application Support/vale/.vale.ini`   |
+| Unix    | `$XDG_CONFIG_HOME/vale/.vale.ini`                    |
+
+(Run the `vale ls-dirs` command to see the exact locations on your system.)
 
 This is different from the other config-defining options (`--config`,
 `VALE_CONFIG_PATH`, etc.) in that it's loaded in addition to, rather than 

content/en/docs/topics/vocab/index.md

@@ -32,7 +32,7 @@ Vocab = Some-Name
 BasedOnStyles = Vale, MyStyle
 ```
 
-Each `Vocab` is a single folder (stored at `<StylesPath>/Vocab/<name>/`)
+Each `Vocab` is a single folder (stored at `<StylesPath>/config/vocabularies/<name>/`)
 consisting of two plain-text files&mdash;`accept.txt` and
 `reject.txt`&mdash;that contain one word, phrase, or regular expression per
 line.
@@ -64,15 +64,20 @@ folder structure:
 ```bash
 $ tree styles
 ├───MyStyle
-├───Vocab
-│   ├───Blog
-│   └───Marketing
+├───config
+│   └───vocabularies
+│       ├───Blog
+│       │   ├───accept.txt
+│       │   └───reject.txt
+│       └───Marketing
+│           ├───accept.txt
+│           └───reject.txt
 └───MyOtherStyle
 ```
 
 Here, our `StylesPath` (`/styles`) contains two styles (`MyStyle` and
 `MyOtherStyle`) and two vocabularies (`Blog` and `Marketing`). You can then
-simply reference these entries by their folder name:
+reference these entries by their folder name:
 
 ```ini title=".vale.ini"
 StylesPath = styles

content/en/docs/vale-cli/installation/index.md

@@ -78,7 +78,7 @@ ENV PATH="/dita-ot-3.6/bin:$PATH"
 ENTRYPOINT ["/bin/vale"]
 ```
 
-## PyPI, npm, ...
+## Other options
 
 - [PyPI](https://pypi.org/project/vale/)
 - [npm](https://www.npmjs.com/package/@ocular-d/vale-bin)

content/en/docs/vale-cli/overview/index.md

@@ -24,17 +24,15 @@ be. To put it succinctly, Vale doesn't teach you *how to* write; it’s a tool
 
 This distinction is particularly important to understand because Vale doesn't
 offer any of its own advice. Instead, it offers a framework for creating and
-enforcing [custom rules][1]. Its approach is much more similar to code linters
-than it is to traditional grammar checkers.
+enforcing [custom rules][1]. Its approach is much more similar to code linters than it is to traditional grammar checkers.
 
 See "[Introducing Vale, an NLP-powered linter for prose][2]" for a more
 detailed explanation.
 
 ## Why should you use Vale?
 
 - It will enforce your own style and can go well beyond traditional
-  writing-related rules. See [GitLab's configuration][5] for an idea of what's
-  possible.
+  writing-related rules.
 
 - It understands [markup][4] well, allowing you to write your content in
   Markdown, AsciiDoc, reStructuredText, and more, without syntax-related false