Repository: commons-fileupload Updated Branches: refs/heads/master 4c4057b8e -> 6c2f3eba4
Minor changes to streaming docs (commas), and remove duplicate 'and' Project: http://git-wip-us.apache.org/repos/asf/commons-fileupload/repo Commit: http://git-wip-us.apache.org/repos/asf/commons-fileupload/commit/6c2f3eba Tree: http://git-wip-us.apache.org/repos/asf/commons-fileupload/tree/6c2f3eba Diff: http://git-wip-us.apache.org/repos/asf/commons-fileupload/diff/6c2f3eba Branch: refs/heads/master Commit: 6c2f3eba46f7c22f330c0d5a18d4d551b1f127b8 Parents: 4c4057b Author: Bruno P. Kinoshita <[email protected]> Authored: Sun Jun 11 16:43:39 2017 +1200 Committer: Bruno P. Kinoshita <[email protected]> Committed: Sun Jun 11 16:43:39 2017 +1200 ---------------------------------------------------------------------- src/site/xdoc/streaming.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/commons-fileupload/blob/6c2f3eba/src/site/xdoc/streaming.xml ---------------------------------------------------------------------- diff --git a/src/site/xdoc/streaming.xml b/src/site/xdoc/streaming.xml index 5f2dd86..a765975 100644 --- a/src/site/xdoc/streaming.xml +++ b/src/site/xdoc/streaming.xml @@ -27,14 +27,14 @@ <section name="Why Streaming?"> <p> The traditional API, which is described in the <a href="using.html">User - Guide</a>, assumes, that file items must be stored somewhere, before + Guide</a>, assumes that file items must be stored somewhere before they are actually accessable by the user. This approach is convenient, because it allows easy access to an items contents. On the other hand, it is memory and time consuming. </p> <p> The streaming API allows you to trade a little bit of convenience for - optimal performance and and a low memory profile. Additionally, the + optimal performance and a low memory profile. Additionally, the API is more lightweight, thus easier to understand. </p> </section> @@ -42,7 +42,7 @@ <section name="How it works"> <p> Again, the <code>FileUpload</code> class is used for accessing the - form fields and fields in the order, in which they have been sent + form fields and fields in the order in which they have been sent by the client. However, the <code>FileItemFactory</code> is completely ignored. </p> @@ -50,7 +50,7 @@ <section name="Parsing the request"> <p> - First of all, do not forget to ensure, that a request actually is a + First of all, do not forget to ensure that a request actually is a a file upload request. This is typically done using the same static method, which you already know from the traditional API. </p>
