third_party/WebKit: fix typos found in comments

third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it is not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com

[tfarina, 2015-11-15 01:33:34]

tfarina@chromium.org changed reviewers:
+ tfarina@chromium.org

[tfarina, 2015-11-15 01:33:34]

Please, do not commit this patch with the following in the CL description.

"And this patch is for my first patch in blink project.
So I really pleased to commit!
Thanks & Regards"

This is not the kind of information that should go in the CL description.

You should describe what you are changing and why.

Thanks!

[tfarina, 2015-11-15 01:33:56]

Description was changed from

==========
Just fix typos in comments

This patch is for only typos in comments.
And this patch is for my first patch in blink project.
So I really pleased to commit!
Thanks & Regards

BUG=

Author add JakeYoon

R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

This patch is for only typos in comments.
And this patch is for my first patch in blink project.
So I really pleased to commit!
Thanks & Regards

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-15 01:37:37]

I will try to use only the kind of information in the CL description.
Thanks your advise.

On 2015/11/15 01:33:34, tfarina wrote:
> Please, do not commit this patch with the following in the CL description.
> 
> "And this patch is for my first patch in blink project.
> So I really pleased to commit!
> Thanks & Regards"
> 
> This is not the kind of information that should go in the CL description.
> 
> You should describe what you are changing and why.
> 
> Thanks!

[JakeYoon, 2015-11-15 01:44:01]

On 2015/11/15 01:33:34, tfarina wrote:
> Please, do not commit this patch with the following in the CL description.
> 
> "And this patch is for my first patch in blink project.
> So I really pleased to commit!
> Thanks & Regards"
> 
> This is not the kind of information that should go in the CL description.
> 
> You should describe what you are changing and why.
> 
> Thanks!

tfarina, 

I have a question. 
If I want to change this CL description, How can I do that?
Please explain to me.

[JakeYoon, 2015-11-15 01:49:16]

On 2015/11/15 01:44:01, JakeYoon wrote:
> On 2015/11/15 01:33:34, tfarina wrote:
> > Please, do not commit this patch with the following in the CL description.
> > 
> > "And this patch is for my first patch in blink project.
> > So I really pleased to commit!
> > Thanks & Regards"
> > 
> > This is not the kind of information that should go in the CL description.
> > 
> > You should describe what you are changing and why.
> > 
> > Thanks!
> 
> tfarina, 
> 
> I have a question. 
> If I want to change this CL description, How can I do that?
> Please explain to me.

Oh... Sorry, I find Edit issue button in this sites.
Thanks!

[JakeYoon, 2015-11-15 01:51:32]

Description was changed from

==========
Just fix typos in comments

This patch is for only typos in comments.
And this patch is for my first patch in blink project.
So I really pleased to commit!
Thanks & Regards

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

This patch is for only typos in comments.
I found typo errors in comments.
So I just fixed typo errors in comments like below example.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-15 01:52:51]

Description was changed from

==========
Just fix typos in comments

This patch is for only typos in comments.
I found typo errors in comments.
So I just fixed typo errors in comments like below example.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

This patch is for only typos in comments.
I found typo errors in comments.
So I just fixed typo errors in comments like below example.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[zino, 2015-11-16 07:40:35]

looks good but you should wait for owner's review.

I think you will be able to add haraken@ as reviewer. He's owner in all of
directories.

[haraken, 2015-11-16 07:46:44]

haraken@chromium.org changed reviewers:
+ haraken@chromium.org

[haraken, 2015-11-16 07:46:45]

https://codereview.chromium.org/1444173002/diff/1/AUTHORS
File AUTHORS (right):

https://codereview.chromium.org/1444173002/diff/1/AUTHORS#newcode248
AUTHORS:248: Jake Yoon <yjaeseok@gmail.com>

Please make this change separately.

[Yuta Kitamura, 2015-11-16 07:49:46]

yutak@chromium.org changed reviewers:
+ yutak@chromium.org

[Yuta Kitamura, 2015-11-16 07:49:47]

https://codereview.chromium.org/1444173002/diff/1/third_party/WebKit/Source/c...
File third_party/WebKit/Source/core/frame/Frame.cpp (right):

https://codereview.chromium.org/1444173002/diff/1/third_party/WebKit/Source/c...
third_party/WebKit/Source/core/frame/Frame.cpp:222: // This is the normal case.
A document can navigate its decendent frames,
descendant?

[JakeYoon, 2015-11-16 08:01:46]

On 2015/11/16 07:49:47, Yuta Kitamura wrote:
>
https://codereview.chromium.org/1444173002/diff/1/third_party/WebKit/Source/c...
> File third_party/WebKit/Source/core/frame/Frame.cpp (right):
> 
>
https://codereview.chromium.org/1444173002/diff/1/third_party/WebKit/Source/c...
> third_party/WebKit/Source/core/frame/Frame.cpp:222: // This is the normal
case.
> A document can navigate its decendent frames,
> descendant?

Yuta I think you are right
I will change this mispellings

[JakeYoon, 2015-11-16 12:40:27]

On 2015/11/16 07:46:45, haraken wrote:
> https://codereview.chromium.org/1444173002/diff/1/AUTHORS
> File AUTHORS (right):
> 
> https://codereview.chromium.org/1444173002/diff/1/AUTHORS#newcode248
> AUTHORS:248: Jake Yoon <mailto:yjaeseok@gmail.com>
> 
> Please make this change separately.

Hello, Haraken.

I separate AUTHORS modify with this patch.
Please, review my patch.

Thanks

[tfarina, 2015-11-16 12:50:36]

Why did you remove chromium-reviews from CC list? Please, don't do this.
Otherwise things get private.

Also, another point, are you a Samsung employee? If yes, why are you not using
your corporate email address?

You should land the Authors patch only after your first patch gets committed,
not before.

Please take your time to review the procedures on submitting patches for review.

[tfarina, 2015-11-16 12:55:50]

The CL description still needs polishment. You are basically repeating yourself
three times in three diferent lines saying that you found typos and are fixing
them. This information is already provided by the subject line.

You might want to try to list in the CL description the mispelled words you
found and probably the method you used to find them. Manually, git grep, script,
another tool?

Please, do not land this before getting a good commit message.

[JakeYoon, 2015-11-16 13:07:47]

On 2015/11/16 12:50:36, tfarina wrote:
> Why did you remove chromium-reviews from CC list? Please, don't do this.
> Otherwise things get private.
> 
> Also, another point, are you a Samsung employee? If yes, why are you not using
> your corporate email address?
> 
> You should land the Authors patch only after your first patch gets committed,
> not before.
> 
> Please take your time to review the procedures on submitting patches for
review.

Hello, tfarina.

Thanks for your response.

First, Because this patch is about typos patches for several parts, it has too
many CC. 
So I thought that "It has too many CC". But, it is my mistake to remove
chromium-reviews from CC list also.
I try to remember do not remove chromium-reviews from CC list.

Second, You are right. I am a Samsung employee. But I cannot access my corporate
email yet. So I used my own email address. Does it make some problem? (please
explain to me about it)

Third, Through this patch, I got to know I can land the Authors patch only after
my first patch gets committed.

Thanks tfarina.

[JakeYoon, 2015-11-16 13:19:59]

On 2015/11/16 13:07:47, JakeYoon wrote:
> On 2015/11/16 12:50:36, tfarina wrote:
> > Why did you remove chromium-reviews from CC list? Please, don't do this.
> > Otherwise things get private.
> > 
> > Also, another point, are you a Samsung employee? If yes, why are you not
using
> > your corporate email address?
> > 
> > You should land the Authors patch only after your first patch gets
committed,
> > not before.
> > 
> > Please take your time to review the procedures on submitting patches for
> review.
> 
> Hello, tfarina.
> 
> Thanks for your response.
> 
> First, Because this patch is about typos patches for several parts, it has too
> many CC. 
> So I thought that "It has too many CC". But, it is my mistake to remove
> chromium-reviews from CC list also.
> I try to remember do not remove chromium-reviews from CC list.
> 
> Second, You are right. I am a Samsung employee. But I cannot access my
corporate
> email yet. So I used my own email address. Does it make some problem? (please
> explain to me about it)
> 
> Third, Through this patch, I got to know I can land the Authors patch only
after
> my first patch gets committed.
> 
> Thanks tfarina.

Ohhh.... tfarina you can misunderstand my response...
In second, I mean that I cannot access my corporate email always for example out
of the office.
This contribution is just my hobby.

Thanks

[JakeYoon, 2015-11-16 13:32:16]

Description was changed from

==========
Just fix typos in comments

This patch is for only typos in comments.
I found typo errors in comments.
So I just fixed typo errors in comments like below example.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors just spellings, It is not always
correct. So, I have tried to check out whether it is correct or not. And If some
typo errors in source code, I do not modify file. Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 13:34:53]

On 2015/11/16 12:55:50, tfarina wrote:
> The CL description still needs polishment. You are basically repeating
yourself
> three times in three diferent lines saying that you found typos and are fixing
> them. This information is already provided by the subject line.
> 
> You might want to try to list in the CL description the mispelled words you
> found and probably the method you used to find them. Manually, git grep,
script,
> another tool?
> 
> Please, do not land this before getting a good commit message.

Hello, tfarina.
I try to make CL description more detail. Please review my CL description?

Thanks

[JakeYoon, 2015-11-16 14:56:29]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors just spellings, It is not always
correct. So, I have tried to check out whether it is correct or not. And If some
typo errors in source code, I do not modify file. Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, It is not
always correct. So, I have tried to check out whether it is correct or not. And
If some typo errors in source code, I do not modify file. Just fix typos in
comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[zino, 2015-11-16 15:35:16]

On 2015/11/16 12:50:36, tfarina wrote:
> Why did you remove chromium-reviews from CC list? Please, don't do this.
> Otherwise things get private.
> 

It's my mistake. I thought many CCs could receive the duplicated mails.
Also, I thought it's unnecessary because this patch is trivial and needs many
stamps from each directory's owner.
Sorry for my incorrect guide.

> Also, another point, are you a Samsung employee? If yes, why are you not using
> your corporate email address?
> 

Yes, he is a Samsung employee but he is not working on Blink or Chromium in our
company.
He's just interested in open source contribution and it's just hobby or exciting
work to him. (although this patch is trivial)
So, I just gave him some guide for contribution as friend and it's not related
to our company.
If there is a problem(e.g. policy), please let us know :)

> You should land the Authors patch only after your first patch gets committed,
> not before.
> 

I and he already know it but we need to be clearer.
I'm not sure but some reviewers guided that the AUTHORS file has to upload with
first code change.
I don't remember where I saw the guide comments but I found some CLs.
 - https://codereview.chromium.org/254463004
 - https://codereview.chromium.org/322503006
Are there a difference between Blink and Chromium?
Anyway, please correct us.

> Please take your time to review the procedures on submitting patches for
review.

Thank you.

[zino, 2015-11-16 15:41:07]

JakeYoon@,

Please rewrite the CL description. Each line should be < 80bytes.

[JakeYoon, 2015-11-16 20:46:11]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, It is not
always correct. So, I have tried to check out whether it is correct or not. And
If some typo errors in source code, I do not modify file. Just fix typos in
comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, It is not
always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 20:53:22]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, It is not
always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 20:54:27]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
-            // Coalesce multiple occurences of the same buffer to the first
index.
+            // Coalesce multiple occurrences of the same buffer to the first
index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
-    // Don't send stop notifications for inital empty documents, since they
don't generate start notifications.
+    // Don't send stop notifications for initial empty documents, since they
don't generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
- // Coalesce multiple occurences of the same buffer to the first index.
+ // Coalesce multiple occurrences of the same buffer to the first index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
- // Don't send stop notifications for inital empty documents, since they don't
generate start notifications.
+ // Don't send stop notifications for initial empty documents, since they don't
generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 20:54:58]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
- // Coalesce multiple occurences of the same buffer to the first index.
+ // Coalesce multiple occurrences of the same buffer to the first index.
third_party/WebKit/Source/core/loader/FrameLoader.cpp:527
- // Don't send stop notifications for inital empty documents, since they don't
generate start notifications.
+ // Don't send stop notifications for initial empty documents, since they don't
generate start notifications.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
- // Coalesce multiple occurences of the same buffer to the first index.
+ // Coalesce multiple occurrences of the same buffer to the first index.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 20:57:54]

On 2015/11/16 15:41:07, zino wrote:
> JakeYoon@,
> 
> Please rewrite the CL description. Each line should be < 80bytes.

zino@,

I modified the CL Description to each line is < 80 Bytes. 
But I want to know How do I know whether each line is < 80 Bytes or not easily?
Please advice.

Thanks

[tfarina, 2015-11-16 21:29:52]

Description was changed from

==========
Just fix typos in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 
But, because this tool found all typo errors from just spellings, 
It is not always correct. 
So, I have tried to check out whether it is correct or not.
And If some typo errors in source code, I do not modify file.
Just fix typos in comments.

For example 
third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp:676
- // Coalesce multiple occurences of the same buffer to the first index.
+ // Coalesce multiple occurrences of the same buffer to the first index.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 

BUG=None
R=jinho.bang@samsung.com
==========

[tfarina, 2015-11-16 21:31:07]

On 2015/11/16 20:57:54, JakeYoon wrote:
> I modified the CL Description to each line is < 80 Bytes. 
> But I want to know How do I know whether each line is < 80 Bytes or not
easily?
That will vary and depends on the text editor you use to write the commit
message. Most of us use Emacs or Vim.

[tfarina, 2015-11-16 21:36:44]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors. 

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

misspellings tool (https://pypi.python.org/pypi/misspellings) were used to find
the typos in the comments.

BUG=None
R=jinho.bang@samsung.com
==========

[tfarina, 2015-11-16 21:36:56]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

misspellings tool (https://pypi.python.org/pypi/misspellings) were used to find
the typos in the comments.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

misspellings tool (https://pypi.python.org/pypi/misspellings) were used
to find the typos in the comments.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 21:42:24]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

misspellings tool (https://pypi.python.org/pypi/misspellings) were used
to find the typos in the comments.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-16 21:43:25]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool found typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-11-17 23:50:30]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2015-12-01 14:49:27]

On 2015/11/16 21:31:07, tfarina wrote:
> On 2015/11/16 20:57:54, JakeYoon wrote:
> > I modified the CL Description to each line is < 80 Bytes. 
> > But I want to know How do I know whether each line is < 80 Bytes or not
> easily?
> That will vary and depends on the text editor you use to write the commit
> message. Most of us use Emacs or Vim.

@tfarlna I am sorry, I think I got in trouble for this patch #3...
I just did "git pull" and then "git cl upload",
But.... it looks like "I got in trouble for some files"
Because some files were changed with other patch.

for example :
in 14:third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp
I didn't add "#include "bindings/core/v8/V8ImageBitmap.h"

Is it Okay?..... Please tell me that... Thanks!

[JakeYoon, 2015-12-01 14:50:32]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it it not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it is not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

[zino, 2015-12-02 04:21:02]

On 2015/12/01 14:49:27, JakeYoon wrote:
> @tfarlna I am sorry, I think I got in trouble for this patch #3...
> I just did "git pull" and then "git cl upload",
> But.... it looks like "I got in trouble for some files"
> Because some files were changed with other patch.
> 
> for example :
> in 14:third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp
> I didn't add "#include "bindings/core/v8/V8ImageBitmap.h"
> 
> Is it Okay?..... Please tell me that... Thanks!

You had to use 'git rebase' instead of 'git pull'.

Let's imagine the following situation.
upstream master : a - b - c - d - e - f - g - h
origin/master : a - b - c - d - e
master : a - b - c - d - e - your patch

You will probably want to have the following status.
upstream master : a - b - c - d - e - f - g - h
origin/master : a - b - c - d - e - f - g - h
master : a - b - c - d - e - f - g - h - your patch

But if you use the 'git pull' command, the local repo status will change as
follows.
origin/master : a - b - c - d - e - f - g - h
master : a - b - c - d - e - your patch - (merged f' - g' - h')

So, you should use the 'git fetch' and 'git rebase <branch>'.
If you do 'git fetch' first, you can sync the origin/master with upstream as
follows.
upstream master : a - b - c - d - e - f - g - h
origin/master : a - b - c - d - e - f - g - h

and then you can use 'git rebase origin/master' command in 'master' checkout.
upstream master : a - b - c - d - e - f - g - h
origin/master : a - b - c - d - e - f - g - h
master : a - b - c - d - e - f - g - h - your patch

But you should rollback first in order to fix the conflicts and then apply
patchset2 using 'git cl patch <issue_number>'.

If you need my help, ping me via messenger.

[JakeYoon, 2015-12-02 14:22:38]

On 2015/12/02 04:21:02, zino wrote:
> On 2015/12/01 14:49:27, JakeYoon wrote:
> > @tfarlna I am sorry, I think I got in trouble for this patch #3...
> > I just did "git pull" and then "git cl upload",
> > But.... it looks like "I got in trouble for some files"
> > Because some files were changed with other patch.
> > 
> > for example :
> > in 14:third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp
> > I didn't add "#include "bindings/core/v8/V8ImageBitmap.h"
> > 
> > Is it Okay?..... Please tell me that... Thanks!
> 
> You had to use 'git rebase' instead of 'git pull'.
> 
> Let's imagine the following situation.
> upstream master : a - b - c - d - e - f - g - h
> origin/master : a - b - c - d - e
> master : a - b - c - d - e - your patch
> 
> You will probably want to have the following status.
> upstream master : a - b - c - d - e - f - g - h
> origin/master : a - b - c - d - e - f - g - h
> master : a - b - c - d - e - f - g - h - your patch
> 
> But if you use the 'git pull' command, the local repo status will change as
> follows.
> origin/master : a - b - c - d - e - f - g - h
> master : a - b - c - d - e - your patch - (merged f' - g' - h')
> 
> So, you should use the 'git fetch' and 'git rebase <branch>'.
> If you do 'git fetch' first, you can sync the origin/master with upstream as
> follows.
> upstream master : a - b - c - d - e - f - g - h
> origin/master : a - b - c - d - e - f - g - h
> 
> and then you can use 'git rebase origin/master' command in 'master' checkout.
> upstream master : a - b - c - d - e - f - g - h
> origin/master : a - b - c - d - e - f - g - h
> master : a - b - c - d - e - f - g - h - your patch
> 
> But you should rollback first in order to fix the conflicts and then apply
> patchset2 using 'git cl patch <issue_number>'.
> 
> If you need my help, ping me via messenger.

Please review again. haraken@, tfarina@, zino@, Yuta Kitamura@ .
At patch #5, I change CL Description (what? why? how?, each line < 80 bytes)
And Typo patch is applied at upstream master.

Thanks & Regards.

[JakeYoon, 2015-12-17 05:01:17]

On 2015/12/02 14:22:38, JakeYoon wrote:
> On 2015/12/02 04:21:02, zino wrote:
> > On 2015/12/01 14:49:27, JakeYoon wrote:
> > > @tfarlna I am sorry, I think I got in trouble for this patch #3...
> > > I just did "git pull" and then "git cl upload",
> > > But.... it looks like "I got in trouble for some files"
> > > Because some files were changed with other patch.
> > > 
> > > for example :
> > > in 14:third_party/WebKit/Source/bindings/core/v8/ScriptValueSerializer.cpp
> > > I didn't add "#include "bindings/core/v8/V8ImageBitmap.h"
> > > 
> > > Is it Okay?..... Please tell me that... Thanks!
> > 
> > You had to use 'git rebase' instead of 'git pull'.
> > 
> > Let's imagine the following situation.
> > upstream master : a - b - c - d - e - f - g - h
> > origin/master : a - b - c - d - e
> > master : a - b - c - d - e - your patch
> > 
> > You will probably want to have the following status.
> > upstream master : a - b - c - d - e - f - g - h
> > origin/master : a - b - c - d - e - f - g - h
> > master : a - b - c - d - e - f - g - h - your patch
> > 
> > But if you use the 'git pull' command, the local repo status will change as
> > follows.
> > origin/master : a - b - c - d - e - f - g - h
> > master : a - b - c - d - e - your patch - (merged f' - g' - h')
> > 
> > So, you should use the 'git fetch' and 'git rebase <branch>'.
> > If you do 'git fetch' first, you can sync the origin/master with upstream as
> > follows.
> > upstream master : a - b - c - d - e - f - g - h
> > origin/master : a - b - c - d - e - f - g - h
> > 
> > and then you can use 'git rebase origin/master' command in 'master'
checkout.
> > upstream master : a - b - c - d - e - f - g - h
> > origin/master : a - b - c - d - e - f - g - h
> > master : a - b - c - d - e - f - g - h - your patch
> > 
> > But you should rollback first in order to fix the conflicts and then apply
> > patchset2 using 'git cl patch <issue_number>'.
> > 
> > If you need my help, ping me via messenger.
> 
> Please review again. haraken@, tfarina@, zino@, Yuta Kitamura@ .
> At patch #5, I change CL Description (what? why? how?, each line < 80 bytes)
> And Typo patch is applied at upstream master.
> 
> Thanks & Regards.

Please review!!... haraken@, tfarina@, zino@, Yuta Kitamura@.
Why don't you review my first patch in chromium?!
I am really looking forward to your review!!

Thanks & Regards.

[JakeYoon, 2015-12-20 05:49:43]

Please review tfarina@, haraken@, Yuta Kitamura@
I am looking forward to your review!

[JakeYoon, 2016-01-04 15:27:43]

Description was changed from

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it is not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

to

==========
third_party/WebKit: fix typos found in comments

I used misspellings tool (https://pypi.python.org/pypi/misspellings).
Misspellings tool find typo errors based on common typo errors.
But, because this tool only found typos error from spellings,
it is not always correct.
So I has checked whether the result of tool correct or not line by line.
And this tool find typo errors in source codes also.
So I check it also to do not change source code.

BUG=None
R=jinho.bang@samsung.com
==========

[JakeYoon, 2016-01-04 15:27:43]

yjaeseok@gmail.com changed reviewers:
+ nednguyen@google.com, phajdan.jr@chromium.org

[JakeYoon, 2016-01-04 15:28:48]

Please review nednguyen@, Pawel Hajdan Jr.@
I am looking forward to your review!