Update README.md

Author: MartinSimango

README.md

@@ -27,33 +27,44 @@ $ kubectl krew install --manifest-url https://github.com/MartinSimango/kubectl-p
 
 The plugin works by reading config files for specfic shells (so far only bash and zsh). These config files in a folder located at `$HOME/.kube/plugin-completion-config` and are named `$SHELL_NAME.yaml`. So for example the zsh config file will be located at `$HOME/.kube/plugin-completion-config/zsh.yaml`. 
 
-The config files contain information about the available kubectl plugins along with some additional information such as plugin's description and the plugin's completion function name. Below is an example of what a config file for a zsh terminal will look like:
+The config files contain information about the available kubectl plugins along with some additional information such as the plugin's description and the plugin's completion function name. Below is an example of what a config file for a zsh terminal will look like:
 
 ```yaml
 shell: zsh
 shellLocation: /bin/zsh
 plugins:
+- name: cert_manager
+  completionFunctionName: ""
+  description: A kubectl plugin called cert_manager
+  supportsCobraCompletion: false
 - name: krew
   completionFunctionName: _krew
   description: A kubectl plugin called krew
+  supportsCobraCompletion: true
+- name: stern
+  completionFunctionName: ""
+  description: A kubectl plugin called stern
+  supportsCobraCompletion: false
 - name: hello
   completionFunctionName: ""
   description: A kubectl plugin called hello
+  supportsCobraCompletion: false
 - name: plugin_completion
   completionFunctionName: _plugin_completion
   description: A kubectl plugin called plugin_completion
+  supportsCobraCompletion: true
 ```
 
 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) 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 a plugin was not created by using [cobra](https://github.com/spf13/cobra) 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:
+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=custom_plugin --completion-function="_completion_function_name"
+$ kubectl plugin_completion config edit zsh --plugin-name=plugin_name --completion-function="_completion_function_name"
 ```
 
 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.