grammar issues

Author: Aslemammad

README.2.md

@@ -1,12 +1,12 @@
-> a video showcasing how pnpm autocompletions works on a test cli command like `my-cli`
+> A video showcasing how pnpm autocompletions work on a test CLI command like `my-cli`
 
 # tab
 
-> instant feedback when hitting [TAB] in your cli tool
+> Instant feedback for your CLI tool when hitting [TAB] in your terminal 
 
-as cli tooling authors, if we can spare our users a second or two by not checking the documentation or writing the `-h` option, we're doing them a huge favor. the unconscious loves hitting the [TAB] key. it always expects feedback. so it feels dissappointing when hitting that key in the terminal but then nothing happens. that frustration is apparent across the whole javascript cli tooling ecosystem.
+As CLI tooling authors, if we can spare our users a second or two by not checking the documentation or writing the `-h` option, we're doing them a huge favor. The unconscious loves hitting the [TAB] key. It always expects feedback. So it feels disappointing when hitting that key in the terminal but then nothing happens. That frustration is apparent across the whole JavaScript CLI tooling ecosystem.
 
-autocompletions are the solution to not break the user's flow. the issue is they're not simple to add. `zsh` expects them in a way, and `bash` in another way. then where do we provide them so the shell environment parses them? too many headaches to ease the user's experience. whether it's worth it or not is out of the question. because tab is the solution to this complexity.  
+Autocompletions are the solution to not break the user's flow. The issue is they're not simple to add. `zsh` expects them in one way, and `bash` in another way. Then where do we provide them so the shell environment parses them? Too many headaches to ease the user's experience. Whether it's worth it or not is out of the question. Because tab is the solution to this complexity.  
 
 `my-cli.ts`:
 ```typescript
@@ -26,7 +26,7 @@ if (process.argv[2] === 'complete') {
 }
 ```
 
-this `my-cli.ts` would be equipped with all the tools required to provide autocompletions. 
+This `my-cli.ts` would be equipped with all the tools required to provide autocompletions. 
 
 ```bash
 node my-cli.ts complete -- "st"
@@ -36,57 +36,70 @@ start   start the development server
 :0
 ```
 
-this output was generated by the `t.parse` method to autocomplete "st" to "start". 
+This output was generated by the `t.parse` method to autocomplete "st" to "start". 
 
-obviously, the user won't be running that command directly in their terminal. they'd be running something like this. 
+Obviously, the user won't be running that command directly in their terminal. They'd be running something like this. 
 
 ```bash
 source <(node my-cli.ts complete zsh) 
 ```
 
-now whenever the shell sees `my-cli`, it would bring the autocompletions we wrote for this cli tool. the `node my-cli.ts complete zsh` part would output the zsh script that loads the autocompletions provided by `t.parse` which then would be executed using `source`.
+Now whenever the shell sees `my-cli`, it would bring the autocompletions we wrote for this CLI tool. The `node my-cli.ts complete zsh` part would output the zsh script that loads the autocompletions provided by `t.parse` which then would be executed using `source`.
 
-the autocompletions are only lived through the current session. to set them up across all of terminal sessions, the autocompletion script should be injected in the `.zshrc` file.
+The autocompletions only live through the current shell session. To set them up across all terminal sessions, the autocompletion script should be injected in the `.zshrc` file.
 
 ```bash
 my-cli complete zsh > ~/completion-for-my-cli.zsh && echo 'source ~/completion-for-my-cli.zsh' >> ~/.zshrc
 ```
 
-this is an example of autocompletions on a global cli command that is usually installed using the `-g` flag (e.g. `npm add -g my-cli`) which is available across the computer. 
+Or 
+
+```bash
+echo 'source <(npx --offline my-cli complete zsh)' >> ~/.zshrc
+```
+
+This is an example of autocompletions on a global CLI command that is usually installed using the `-g` flag (e.g. `npm add -g my-cli`) which is available across the computer. 
 
 ---
 
-while working on tab, we came to the realization that most javascript clis are not global cli commands but rather, per-project dependencies. 
+While working on tab, we came to the realization that most JavaScript CLIs are not global CLI commands but rather, per-project dependencies. 
 
-for instance, vite won't be installed globally and instead it'd be always installed on a project. here's an example usage:
+For instance, Vite won't be installed globally and instead it'd be always installed on a project. Here's an example usage:
 
 ```bash
-pnpm vite -h
+pnpm vite dev
 ```
 
-so in this case, a computer might have hundreds of vite instances each installed separately and potentially from different versions on different projects. 
+Rather than installing it globally. This example is pretty rare: 
 
-we were looking for a fluid strategy that would be able to load the autocompletions from each of these dependencies on a per-project basis. 
+```bash
+vite dev
+```
+
+So in this case, a computer might have hundreds of Vite instances each installed separately and potentially from different versions on different projects. 
 
-and that made us develop our own autocompletion abstraction over npm, pnpm and yarn. this would help tab identify which binaries are avaialble in a project and which of these binaries provide autocompletions. so the user would not have to `source` anything or inject any script in their `.zshrc`. 
+We were looking for a fluid strategy that would be able to load the autocompletions from each of these dependencies on a per-project basis. 
 
-they'd only have to run this command once and inject it in their shell config. 
+And that made us develop our own autocompletion abstraction over npm, pnpm and yarn. This would help tab identify which binaries are available in a project and which of these binaries provide autocompletions. So the user would not have to `source` anything or inject any script in their `.zshrc`. 
+
+They'd only have to run this command once and inject it in their shell config. 
 
 ```bash
-echo 'eval "$(npx --prefer-offline @bombsh/tab pnpm zsh)"' >> ~/.zshrc
+npx @bombsh/tab pnpm zsh
 ```
 
---- 
+These autocompletions on top of the normal autocompletions that these package managers provide are going to be way more powerful.
 
-```typescript
-import t from '@bombsh/tab'
-
-t.option('help', 'list available commands') // Command (Root) 
+These new autocompletions on top of package managers would help us with autocompletions on commands like `pnpm vite` and other global or per-project binaries. The only requirement would be that the npm binary itself would be a tab-compatible binary.  
 
-t.command('start', 'start the development server') // Command ('start')
- .option('port', 'specify the port number') // Command ('port')
+What is a tab-compatible binary? It's a tool that provides the `complete` subcommand that was showcased above. Basically any CLI tool that uses tab for its autocompletions is a tab-compatible binary.
 
-t.parse(process.argv.slice(3)) 
+```bash
+pnpm my-cli complete --
+```
+```
+start   start the development server
+:0
+```
 
-t.setup(process.argv[2], x)
-```
+We are planning to maintain these package manager autocompletions on our own and turn them into full-fledged autocompletions that touch on every part of our package managers.