docs/memory-infra/heap_profiler.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/memory-infra/heap_profiler.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/memory-infra/heap_profiler.md

diff --git a/docs/memory-infra/heap_profiler.md b/docs/memory-infra/heap_profiler.md

index 57961d350948ad50ed168ba233c1ba1692912ced..0910b641bf2ab9b2e67b123158964e99f3232f57 100644

--- a/docs/memory-infra/heap_profiler.md

+++ b/docs/memory-infra/heap_profiler.md

@@ -2,7 +2,7 @@

As of Chrome 48, MemoryInfra supports heap profiling. The core principle is

a solution that JustWorks™ on all platforms without patching or rebuilding,

-intergrated with the chrome://tracing ecosystem.

+integrated with the chrome://tracing ecosystem.

[TOC]

@@ -121,7 +121,7 @@ size concerns. Development builds have full type information.

To keep the trace log small, uninteresting information is omitted from heap

dumps. The long tail of small nodes is not dumped, but grouped in an `<other>`

-node instead. Note that altough these small nodes are insignificant on their

+node instead. Note that although these small nodes are insignificant on their

own, together they can be responsible for a significant portion of the heap. The

`<other>` node is large in that case.

« no previous file with comments | « docs/memory-infra/README.md ('k') | docs/optional.md » ('j') | no next file with comments »