[ 
https://issues.apache.org/jira/browse/HADOOP-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407341#comment-16407341
 ] 

Sean Mackrory commented on HADOOP-15332:
----------------------------------------

{quote}

@@ -1569,10 +1569,10 @@ from VMs running on EC2.
 There are two mechanisms for cleaning up after leftover multipart
 uploads:
 - Hadoop s3guard CLI commands for listing and deleting uploads by their
-age. Doumented in the [S3Guard](./s3guard.html) section.
+age. Documented in the [S3Guard](./s3guard.html) section.
 - The configuration parameter `fs.s3a.multipart.purge`, covered below.
 
-If an large stream writeoperation is interrupted, there may be
+If an large stream write operation is interrupted, there may be
 intermediate partitions uploaded to S3 —data which will be billed for.
 
 These charges can be reduced by enabling `fs.s3a.multipart.purge`,

{quote}

Now that's a tricky section of patch to review :) Was wondering why you removed 
the lines "Hadoop s3guard CLI..." and "The configuration parameter" until I 
noticed the space. Should also be "a" large stream, not "an large stream", but 
that's laughably trivial and I can just fix it when I commit.

> Fix typos in hadoop-aws markdown docs
> -------------------------------------
>
>                 Key: HADOOP-15332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15332
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Gabor Bota
>            Assignee: Gabor Bota
>            Priority: Minor
>         Attachments: HADOOP-15332.patch
>
>
> While reading through 
> https://github.com/apache/hadoop/tree/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws
>  I've found some very obvious typos, and I thought it would be a nice 
> improvement to fix those.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to