소스 검색

Doc fix: Line feed, not carriage return.

Andreas Stührk 10 년 전
부모
커밋
347cf1201f
1개의 변경된 파일2개의 추가작업 그리고 2개의 파일을 삭제
  1. 2 2
      docs/events.rst

+ 2 - 2
docs/events.rst

@@ -260,7 +260,7 @@ After the event listener has processed the event serialization, in
 order to notify supervisord about the result, it should send back a
 order to notify supervisord about the result, it should send back a
 result structure on its stdout.  A result structure is the word
 result structure on its stdout.  A result structure is the word
 "RESULT", followed by a space, followed by the result length, followed
 "RESULT", followed by a space, followed by the result length, followed
-by a carriage return, follwed by the result content.  For example,
+by a line feed, followed by the result content.  For example,
 ``RESULT 2\nOK`` is the result "OK".  Conventionally, an event
 ``RESULT 2\nOK`` is the result "OK".  Conventionally, an event
 listener will use either ``OK`` or ``FAIL`` as the result content.
 listener will use either ``OK`` or ``FAIL`` as the result content.
 These strings have special meaning to the default result handler.
 These strings have special meaning to the default result handler.
@@ -280,7 +280,7 @@ Once the listener is in the ``ACKNOWLEDGED`` state, it may either exit
 ``autorestart`` config parameter is ``true``), or it may continue
 ``autorestart`` config parameter is ``true``), or it may continue
 running.  If it continues to run, in order to be placed back into the
 running.  If it continues to run, in order to be placed back into the
 ``READY`` state by supervisord, it must send a ``READY`` token
 ``READY`` state by supervisord, it must send a ``READY`` token
-followed immediately by a carriage return to its stdout.
+followed immediately by a line feed to its stdout.
 
 
 Example Event Listener Implementation
 Example Event Listener Implementation
 +++++++++++++++++++++++++++++++++++++
 +++++++++++++++++++++++++++++++++++++