Merge pull request #11 from joshuaa/patch-1

Clarify the distinction between commands and pipes

docs/UsersGuide/user/cmd-evt-chn-prm.md

@@ -23,10 +23,10 @@ These types will be elaborated within this guide. It contains:
 
 ## Commands
 
-Each **Component** defines a set of commands it handels. Commands are defined through a series of properties. Each
-command can be sent to the F´ system and via `Svc::CmdDispatcher` these commands are dispatched to a handling component
-to invoke some behavior. The handling component handles a command by defining a command handler function to run when the
-command arrives.
+Each **Component** defines a set of commands for operations. Unlike pipes, which are intended for component to component communication, commands are designed for user interaction with a component. Commands are defined through a series of 
+properties. Users can send commands to the F´ system and via `Svc::CmdDispatcher` these commands are dispatched to a 
+handling component to invoke some behavior. The handling component handles a command by defining a command handler function 
+to run when the command arrives.
 
 The properties defining commands are shown below:
 
@@ -176,4 +176,4 @@ command.
 ## A Note On Serialized Ports
 
 The `Svc` components use serialize ports to generically handle port data of different types to support uplink and
-downlink.
+downlink.