Bug 506041 Part 2: Correct misspellings in source code
r=timeless
This commit is contained in:
Родитель
4489fde9b0
Коммит
22d09b8135
|
@ -216,7 +216,7 @@ FeedConverter.prototype = {
|
|||
// to always use this stream converter, even when an auto-action is
|
||||
// specified, not the basic one provided by WebContentConverter. This
|
||||
// converter needs to consume all of the data and parse it, and based on
|
||||
// that determination make a judgement about type.
|
||||
// that determination make a judgment about type.
|
||||
//
|
||||
// Since there are no content types for this content, and I'm not going to
|
||||
// invent any, the upshot is that while a user can set an auto-handler for
|
||||
|
|
|
@ -1289,7 +1289,7 @@ Transparency is important even if you don't know enough about
|
|||
programming or security to determine whether the program
|
||||
contains any flaws. The very fact that it can be examined
|
||||
by anybody allows those with the required expertise to pass
|
||||
judgement, and you can form your own conclusions based on
|
||||
judgment, and you can form your own conclusions based on
|
||||
their analysis.
|
||||
</p>
|
||||
|
||||
|
|
|
@ -68,7 +68,7 @@ static const PRInt32 kNameSpaceID_None = 0;
|
|||
{ 0xac, 0x95, 0x9e, 0x10, 0x24, 0x30, 0x88, 0xd6 } }
|
||||
|
||||
/**
|
||||
* The Name Space Manager tracks the associtation between a NameSpace
|
||||
* The Name Space Manager tracks the association between a NameSpace
|
||||
* URI and the PRInt32 runtime id. Mappings between NameSpaces and
|
||||
* NameSpace prefixes are managed by nsINameSpaces.
|
||||
*
|
||||
|
|
|
@ -180,7 +180,7 @@ nsMIMEHeaderParamImpl::GetParameterInternal(const char *aHeaderValue,
|
|||
;
|
||||
|
||||
// Some broken http servers just specify parameters
|
||||
// like 'filename' without sepcifying disposition
|
||||
// like 'filename' without specifying disposition
|
||||
// method. Rewind to the first non-white-space
|
||||
// character.
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
inline - Used for selected internal functions for which inlining
|
||||
may improve performance on some platforms.
|
||||
|
||||
Note: Use of these macros is based on judgement, not hard rules,
|
||||
Note: Use of these macros is based on judgment, not hard rules,
|
||||
and therefore subject to change.
|
||||
*/
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче