Update our motivation page + Fix minor issues

Author: ZakaHaceCosas

docs/about/branding.md

@@ -10,7 +10,7 @@ You can use our logo just as you'd use any app's logo in a post, video, or any k
 
 ## The name
 
-Ideally, capitalize it as FuckingNode. Preferably use the **Mona Sans** typography, and [open source font](https://github.com/mona-sans) we use for our main branding. The asterisk (F*ckingNode) is optional. If used, censor the U and not any other letter (avoid things like <s>F\*\*kingNode</s>).
+Ideally, capitalize it as FuckingNode. Preferably use the **Mona Sans** typography, an [open source font](https://github.com/mona-sans) we use for our main branding. The asterisk (F*ckingNode) is optional. If used, censor the U and not any other letter (avoid things like <s>F\*\*kingNode</s>).
 
 ### Can acronyms or abbreviations be used?
 

docs/about/why.md

@@ -2,7 +2,7 @@
 
 ## What we wanted to fix
 
-FuckingNode exists because of the many problems that exist and a JavaScript developer may encounter, including but not limited to:
+FuckingNode exists because of the many problems that a JavaScript developer can encounter, including but not limited to:
 
 - How tiring it is to go through all of your projects to update dependencies.
 - How boring it is to manually make "Lint code" or "Format code" commits periodically.
@@ -16,53 +16,48 @@ _And the list goes on..._
 
 ## What we fixed, and how
 
-I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into three major releases, seven separate utilities (`clean`, `kickstart`, `release`, `commit`, `surrender`, `setup`, `stats`) with more to come (like the work in progress `audit`), DenoJS & BunJS support, and even a small amount of features bridged to Go and Cargo (Rust).
+I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into four major releases, eleven separate utilities (`clean`, `kickstart`, `release`, `commit`, `surrender`, `setup`, `stats`, `launch`, `build`, `migrate`, `audit`), DenoJS & BunJS support, and even a small amount of features bridged to Go and Cargo.
 
 FuckingNode is a thing because it fixes all of the issues mentioned above.
 
-### Bored of manually updating dependencies, linting code, or prettifying code?
-
-### Bored of committing all of that?
-
-### Bored of removing built output / artifacts?
+### Bored of manually updating dependencies, linting code, or prettifying code? Of committing all of that? Of removing built output / artifacts?
 
 - [X] `fuckingnode clean -- -- --lint --pretty --commit --destroy --update`
-  - Shorthand: `fkclean -- -- -l -p -c -d -u`
-  - Assuming [flagless features](../manual/fknode-yaml.md#flagless) are enabled, it can be shortened to just `fkclean`
+  - Shorthand: `fkclean -- -- -l -p -c -d -u`.
+  - Assuming [flagless features](../manual/fknode-yaml.md#flagless) are enabled, it can be shortened to just `fkclean`.
 
 ### Bored of finding and pasting or writing your own `tsconfig.json`?
 
-- [X] `fuckingnode setup <path> ts-strictest`
-  - `<path>` is the path to the project, or `--self` to use the CWD.
-  - `ts-strictest` is an example, there are more setups available. Run `fuckingnode setup` with no args to see them all.
+- [X] `fuckingnode setup ts-strictest`
+  - `ts-strictest` is an example, there are more setups available. Run `fuckingnode setup` to see them all.
 
 ### Bored of manually cloning, installing, and launching?
 
 - [X] `fuckingnode kickstart <git-url> [path] [manager]`
   - Shorthand: `fkstart <git-url> [path] [manager]`
+  - `<git-url>` can be not just a Git URL, but also a shorthand (e.g., `gh:Owner/Repo` for GitHub, or `gl:*` for GitLab).
   - `[path]` is optional and specifies a custom path to clone to.
   - `[manager]` is optional and overrides the package manager to use for this project.
 
 ### Bored of manually writing a deprecation notice?
 
 - [X] `fuckingnode surrender <path> [message] [alternatives] [learn-more]`
-  - `<path>` is the path to the project, or `--self` to use the CWD.
+  - `<path>` is the path to the project, or `.` to use the CWD.
   - `[message]` is optional and adds a custom message.
   - `[alternatives]` is optional and lets you write about alternatives to what is going to be deprecated.
   - `[learn-more]` is optional and lets you write a text or link about where the user can learn more about this deprecation.
 
 ### Scared of the pain of making a commit forgetting your tests?
 
-- [X] `fuckingnode commit <message> [branch] [--push]`
-  - Shorthand: `fkcommit <message> [branch] [--push]`
+- [X] `fuckingnode commit <message> <...files> [--branch=x] [--push]`
+  - Shorthand: `fkcommit <message> <...files> [--branch=x] [--push]`
   - `<message>` is your commit message.
-  - `[branch]` is optional and specifies the branch to commit to. If unspecified, current branch is used.
+  - `--branch=*` is optional and specifies the branch to commit to. If unspecified, current active branch is used.
   - `--push` is optional and if passed the commit (and any previous local commit) will be pushed.
 
 ### Tired of the annoyance of npm or jsr package releases?
 
-- [X] `fuckingnode release <path> <version> [--push] [--dry]`
-  - `<path>` is the path to the project, or `--self` to use the CWD.
+- [X] `fuckingnode release <version> [--push] [--dry]`
   - `<version>` is the version to be released, we'll auto bump your package file's version field and create a Git tag with this version code. Must be SemVer parsable.
   - `--push` is optional and if passed, changes will be pushed to Git.
   - `--dry` is optional and if passed, changes will be done (and pushed if specified), but not published to npm / jsr.

docs/manual/index.md

@@ -32,7 +32,7 @@ Install it for your platform following [the instructions here](./install.md) (ju
 
 ### Step 1
 
-Add your projects to FuckingNode's project list. This is done manually with the `fuckingnode add <path>` (or `fkadd <path>`) command. `<path>` can be any file path, or `--self` to use the CWD.
+Add your projects to FuckingNode's project list. This is done manually with the `fuckingnode add <path>` (or `fkadd <path>`) command. `<path>` can be any file path, or `.` to use the CWD.
 
 ```bash
 # relative
@@ -41,10 +41,10 @@ fuckingnode add "../projects/project1"
 fuckingnode add "/home/Zaka/Code/project2"
 # self path
 cd project3
-fuckingnode add --self
+fuckingnode add .
 ```
 
-It's recommended that from now on you run `fkadd --self` immediately after running `npm init` (or `pnpm init` or whatever) each time you create a project.
+It's recommended that from now on you run `fkadd .` immediately after running `npm init` (or `pnpm init` or whatever) each time you create a project.
 
 ### Step 2