[PATCH v2 3/4] trace-cmd reset: Update man page for -k option

Talk about the new -k command line parameter of "trace-cmd reset" in the
trace-cmd man page.

While we are here, fix typo 'immediatly'.

Signed-off-by: Metin Kaya <[email protected]>
---
 Documentation/trace-cmd/trace-cmd-reset.1.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/Documentation/trace-cmd/trace-cmd-reset.1.txt b/Documentation/trace-cmd/trace-cmd-reset.1.txt
index eee86751..026232ac 100644
--- a/Documentation/trace-cmd/trace-cmd-reset.1.txt
+++ b/Documentation/trace-cmd/trace-cmd-reset.1.txt
@@ -60,7 +60,7 @@ significant. See EXAMPLES.
 *-d*::
     This option deletes the instance buffer(s) specified by the most recently
     preceding *-B* or *-a* option. Because the top-level instance buffer
-    cannot be deleted, it is invalid to use this immediatly following *-t* or
+    cannot be deleted, it is invalid to use this immediately following *-t* or
     prior to any *-B* or *-a* option on the command line.
 
 *-t*::
@@ -68,6 +68,12 @@ significant. See EXAMPLES.
     this is the same as the default. But if *-B* or *-a* is used, this is
     required if the top level instance buffer should also be reset.
 
+*-k* 'dynevent-name'::
+    This option allows preserving specified dynamic event during reset. Valid
+    parameters are *kprobe*, *kretprobe*, *uprobe*, *uretprobe*, *eprobe*,
+    *synth* and *all* (for keeping all dynamic events). This may be used
+    multiple times to specify different dynamic event types.
+
 EXAMPLES
 --------
 
@@ -94,6 +100,10 @@ instance buffers exist, they will be unaffected:
 
     trace-cmd reset -b 1024
 
+Prevent *kprobes* and *kretprobes* from being destroyed during reset:
+
+    trace-cmd reset -k kprobe -k kretprobe
+
 
 SEE ALSO
 --------
-- 
2.34.1