Update README.md

Author: MartinSimango

README.md

@@ -2,7 +2,7 @@
 
 > :warning: **Notice**
 > * This has been tested on for kubectl v1.23 and has not been tested on the kubectl v1.24.
-> * Not all kubectl plugins have been tested. You can find a listed of tested plugins at [here](https://github.com/MartinSimango/kubectl-plugin_completion/blob/main/tested-plugins.txt). Please not if a plugin hasn't been tested
+> * Not all kubectl plugins have been tested. You can find a listed of tested plugins at [here](https://github.com/MartinSimango/kubectl-plugin_completion/blob/main/tested-plugins.txt). Please note if a plugin hasn't been tested
 > it might cause unwanted errors such as your shell hanging.
 > * Plugin only supports zsh and bash shells (for now).
 
@@ -40,40 +40,40 @@ The config files contain information about the available kubectl plugins along w
 shell: zsh
 shellLocation: /bin/zsh
 plugins:
-- name: cert_manager
+- name: access_matrix
   completionFunctionName: ""
-  description: A kubectl plugin called cert_manager
+  description: 'Show an RBAC access matrix for server resources '
   supportsCobraCompletion: false
-- name: krew
-  completionFunctionName: _krew
-  description: A kubectl plugin called krew
+- name: accurate
+  completionFunctionName: _accurate
+  description: 'Manage Accurate, a multi-tenancy controller '
   supportsCobraCompletion: true
-- name: stern
+- name: allctx
   completionFunctionName: ""
-  description: A kubectl plugin called stern
-  supportsCobraCompletion: false
-- name: hello
-  completionFunctionName: ""
-  description: A kubectl plugin called hello
+  description: 'Run commands on contexts in your kubeconfig '
   supportsCobraCompletion: false
 - name: plugin_completion
   completionFunctionName: _plugin_completion
-  description: A kubectl plugin called plugin_completion
+  description: A kubectl plugin for allowing shell completions for kubectl plugins
   supportsCobraCompletion: true
+kubectlOverridePlugins:
+- allctx
 ```
 
 The above file can be generated by running: 
 ``` sh
 $ kubectl plugin_completion config generate 
 ```
-This will generate config files for all supported shells (zsh and bash). For plugins that were created using [cobra](https://github.com/spf13/cobra) and have that have a cobra completion command the `completionFunctionName` field will automatically be field in. The description for each plugin will default to: "A kubectl plugin called $plugin_name". 
+This will generate config files for all supported shells (zsh and bash). For plugins that were created using [cobra](https://github.com/spf13/cobra) and have that have a cobra completion command the `completionFunctionName` field will automatically be field in. The description for each plugin will default to: "A kubectl plugin called $plugin_name" if the plugin is not found in the krew repository. 
 
 If a plugin was not created by using [cobra](https://github.com/spf13/cobra) or if the plugin was created using cobra but does not have a completion subcommand, it will be up to you to manually edit the config file and provide the name of the plugin's completion function name. This can also be done by running the `kubectl plugin_completion config edit` command as shown below:
 
 ```sh
 $ kubectl plugin_completion config edit zsh --plugin-name=plugin_name --completion-function="_completion_function_name"
 ```
 
+Plugins who's completion script override the default kubectl completion function such as the allctx plugin can be added to the kubectlOverridePlugins array. Thus typing `kubectl allctx <TAB><TAB>` will still give completions for the kubectl command.
+
 The plugin_completion uses config files to generate completions specific shells in order to allow for completions for kubectl plugins. The generated completion scripts overwrite the behaviour of the completion function for the kubectl tool and extend it to allow for kubectl plugin completions.
 
 ## How to use