docs/memory/key_concepts.md - Issue 2944533002: Fix typo in the memory doc.

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/key_concepts.md

Issue 2944533002: Fix typo in the memory doc. (Closed)

Patch Set: Created 3 years, 6 months 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/key_concepts.md

diff --git a/docs/memory/key_concepts.md b/docs/memory/key_concepts.md

index e8c4942d6e7c0a68e42fba8fef6ebbb1496a6fd3..507a94efc9211f5652eaf1566ba51c9fc7cf2466 100644

--- a/docs/memory/key_concepts.md

+++ b/docs/memory/key_concepts.md

@@ -19,7 +19,7 @@ is complicated stuff...but don't despair. You work on a multi-process

browser implementing the web platform with high security guarantees.

Compared to the rest the system, memory is not THAT complicated.

-## An you give specific examples of how it's harder than malloc/free?

+## Can you give specific examples of how it's harder than malloc/free?

Here are some example questions that require a more complex

view of memory than malloc/free.

« no previous file with comments | « no previous file | no next file » | no next file with comments »