From 9fc9d196b73838842fb2e3e7d9c84d17e1c7fdec Mon Sep 17 00:00:00 2001 From: Todd Leonhardt Date: Wed, 11 Jul 2018 21:10:50 -0400 Subject: Fix a couple minor typos in hooks.rst --- docs/hooks.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/hooks.rst b/docs/hooks.rst index 0ec5d7e9..caeef75b 100644 --- a/docs/hooks.rst +++ b/docs/hooks.rst @@ -94,7 +94,7 @@ of your application. Methods registered for a hook are called in the order they were registered. You can register a function more than once, and it will be called each time it was registered. -Postparsing, precomamnd, and postcommand hook methods share some common ways to +Postparsing, precommand, and postcommand hook methods share some common ways to influence the command processing loop. If a hook raises a ``cmd2.EmptyStatement`` exception: @@ -113,7 +113,7 @@ Postparsing Hooks ^^^^^^^^^^^^^^^^^ Postparsing hooks are called after the user input has been parsed but before -execution of the comamnd. These hooks can be used to: +execution of the command. These hooks can be used to: - modify the user input - run code before every command executes @@ -327,4 +327,4 @@ the various hook methods, presented in chronological order starting with the one .. automethod:: cmd2.cmd2.Cmd.postcmd -.. automethod:: cmd2.cmd2.Cmd.postparsing_postcmd \ No newline at end of file +.. automethod:: cmd2.cmd2.Cmd.postparsing_postcmd -- cgit v1.2.1