You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by ch...@apache.org on 2017/06/13 12:53:17 UTC
[4/7] commons-fileupload git commit: Minor changes to streaming docs
(commas), and remove duplicate 'and'
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/e0a5ef2a
Tree: http://git-wip-us.apache.org/repos/asf/commons-fileupload/tree/e0a5ef2a
Diff: http://git-wip-us.apache.org/repos/asf/commons-fileupload/diff/e0a5ef2a
Branch: refs/heads/master
Commit: e0a5ef2a27fcbaa63bf97da8442096b5183a7961
Parents: 1ac3709
Author: Bruno P. Kinoshita <br...@yahoo.com.br>
Authored: Sun Jun 11 16:43:39 2017 +1200
Committer: Rob Tompkins <ch...@gmail.com>
Committed: Tue Jun 13 08:35:22 2017 -0400
----------------------------------------------------------------------
src/site/xdoc/streaming.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/commons-fileupload/blob/e0a5ef2a/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>