typo in src/docbkx/nio-ext.xml
------------------------------

                 Key: HTTPCORE-250
                 URL: https://issues.apache.org/jira/browse/HTTPCORE-250
             Project: HttpComponents HttpCore
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 4.1
         Environment: 
http://hc.apache.org/httpcomponents-core-ga/tutorial/html/nio.html
            Reporter: Neeme Praks
            Priority: Minor
         Attachments: nio-typo-diff.txt

Section "2.4. I/O reactor exception handling", text "are to be expected are to 
be" should be "are to be expected and are to be".
Section "2.5.6. Direct channel I/O", it is not clear, what is meant by 
"delimited and identity" in "such as Content-Length delimited and identity can 
leverage". I have added questionmarks in diff, for easier navigation.
Section "2.7. Non-blocking HTTP entities", text "!HttpEntity" should be 
"HttpEntity".

Section "2.8.3.2. Throttling protocol handlers", text 
"The throttling protocol handlers allocate input / output buffers of constant 
length upon initialization and control the rate of I/O events in order to 
ensure those content buffers do not ever overflow."
should be
"The throttling protocol handlers allocate input / output buffers of a constant 
length upon initialization and control the rate of I/O events in order to 
ensure those content buffers does not ever overflow."

Section "2.8.3.2. Throttling protocol handlers", text "!Executor" should be 
"Executor".
Section "2.9.1.1. SSL I/O session handler", text "!SSLSession" should be 
"SSLSession".
Section "2.9.2. SSL I/O event dispatches", text "ensure correct handling of the 
SSL protocol handshaking" should be "ensure correct handling of SSL protocol 
handshaking".


-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to