docs/chrome_settings.md - Issue 2551513002: Fix spelling mistakes in //docs.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: docs/chrome_settings.md

Issue 2551513002: Fix spelling mistakes in //docs. (Closed)

Patch Set: Undo beng->being Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: docs/chrome_settings.md

diff --git a/docs/chrome_settings.md b/docs/chrome_settings.md

index fbd44f426d3a5d4e89b8aaa8d41733ab786d959d..69893c5b8f7de6a7b2484b221a7f0a5838aa6120 100644

--- a/docs/chrome_settings.md

+++ b/docs/chrome_settings.md

@@ -78,7 +78,7 @@ For simple prefs, the UI is kept in sync with the value automagically (see

`CoreOptionsHandler`). Find the handler most closely relevant to your pref. The

only action we need take here is to make the page aware of the new string.

Locate the method in the handler called `GetLocalizedStrings` and look at its

-body for examples of `SetString` usage. The first parameter is the javascript

+body for examples of `SetString` usage. The first parameter is the JavaScript

name for the string.

### 4. HTML/CSS/JS

« no previous file with comments | « docs/browser_view_resizer.md ('k') | docs/clang_tool_refactoring.md » ('j') | no next file with comments »