From b08d85ed8036b8d11737c61221b2ae277693120c Mon Sep 17 00:00:00 2001
From: Kohsuke Kawaguchi <kk@kohsuke.org>
Date: Mon, 31 Mar 2014 18:25:11 -0700
Subject: [PATCH] Clarify that this is for a single argument.

issue #24 highlights the confusion
---
 README.markdown | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.markdown b/README.markdown
index a6d7fbc..7486144 100644
--- a/README.markdown
+++ b/README.markdown
@@ -180,11 +180,14 @@ Winsw will then wait for the two processes to exit on its own, before reporting
 When you use the `<stopargument>`, you must use `<startargument>` instead of `<argument>`. See the complete example below:
 
     <executable>catalina.sh</executable>
+    <startargument>jpda</startargument>
     <startargument>run</startargument>
     
     <stopexecutable>catalina.sh</stopexecutable>
     <stopargument>stop</stopargument>
 
+Note that the name of the element is `startargument` and not `startarguments`. As such, to specify multiple arguments, you'll specify multiple elements.
+
 ### stoptimeout
 When the service is requested to stop, winsw first attempts to <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms683155(v=vs.85).aspx">send Ctrl+C signal to the process</a>, then wait for up to 15 seconds for the process to exit by itself gracefully. A process failing to do that (or if the process does not have a console), then winsw resorts to calling <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms686714(v=vs.85).aspx">TerminateProcess</a> API to kill the service instantly.