summaryrefslogtreecommitdiff
path: root/technical/reviews/talks.md
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2019-05-04 22:37:55 +0200
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2019-05-04 22:41:06 +0200
commita3bd3c43fa8faa9c0fe6aaa6dfa02e3d3d8bdbb9 (patch)
treec519c9f7ced12a5370f0c8ae093612d618ee96ac /technical/reviews/talks.md
parentc3e13f4ede83d4ea4047f100a26a7f1a08720879 (diff)
downloadmemory-leaks-a3bd3c43fa8faa9c0fe6aaa6dfa02e3d3d8bdbb9.tar.xz
Fix typo
Diffstat (limited to 'technical/reviews/talks.md')
-rw-r--r--technical/reviews/talks.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/technical/reviews/talks.md b/technical/reviews/talks.md
index 93ff44d..ed272c8 100644
--- a/technical/reviews/talks.md
+++ b/technical/reviews/talks.md
@@ -38,8 +38,8 @@ programmer starting to apply these rules: the programmer wonders when
they will be able to understand the new application "the same way"
they understood the old one. I.e. will they ever reach a point where
they have a complete mental map of every interaction between every
-object, the same way the used to have a complete mental map of the old
-monolithic, sequential application?
+object, the same way they used to have a complete mental map of the
+old monolithic, sequential application?
Metz's response is that nope, this will never happen; they will "cease
to care" instead. In exchange, they will be able to make localized