docs: lx check -> lx lint

Author: Marc Jakobi

docs/guides/formatting-linting.md

@@ -35,15 +35,15 @@ Linting is the process of analyzing code for stylistic and logic error (lines to
 Lux comes with `luacheck`, a linter for Lua code, built-in. To run `luacheck` on your project, use the following command:
 
 ```sh
-lx check
+lx lint
 ```
 
 We recommend running this automatically through a git hook, or running it manually at the end of every significant
 addition/refactor of your code.
 
 ## Git Hooks
 
-We recommend setting up a Git hook to run `lx check` and `lx fmt` before
+We recommend setting up a Git hook to run `lx lint` and `lx fmt` before
 each commit to ensure that you never forget to lint and format your code.
 
 To set up a Git hook, create a file called `.git/hooks/pre-commit` in your
@@ -52,7 +52,7 @@ project directory with the following content:
 ```sh
 #!/bin/sh
 
-lx check
+lx lint
 lx fmt
 ```
 

docs/tutorial/07-code-hygiene.md

@@ -6,16 +6,16 @@ title: Code Hygiene
 Code hygiene is the practice of writing code that is readable and maintainable.
 In this chapter, we'll let tools automatically clean up our code for us.
 
-## Linting with `lx check`
+## Linting with `lx lint`
 
 Linting is the process of analyzing code for potential errors and stylistic issues (lines too long, unused variables, etc.).
 To lint the entire project, we can run:
 
 ```sh
-lx check
+lx lint
 ```
 
-<!--TODO: show output of lx check and fix the errors that exist there-->
+<!--TODO: show output of lx lint and fix the errors that exist there-->
 
 ## Formatting with `lx fmt`