From a9609842f7ca84c5f7cdd7670e8cb0a9e365d235 Mon Sep 17 00:00:00 2001 From: Ghost-017 <31908292+Ghost-017@users.noreply.github.com> Date: Sat, 19 Oct 2019 20:27:51 +0800 Subject: [PATCH] minor --- 2-ui/99-ui-misc/01-mutation-observer/article.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/2-ui/99-ui-misc/01-mutation-observer/article.md b/2-ui/99-ui-misc/01-mutation-observer/article.md index f1e10369..4d36d7ae 100644 --- a/2-ui/99-ui-misc/01-mutation-observer/article.md +++ b/2-ui/99-ui-misc/01-mutation-observer/article.md @@ -3,7 +3,7 @@ `MutationObserver` is a built-in object that observes a DOM element and fires a callback in case of changes. -We'll first see syntax, and then explore a real-world use case. +We'll first take a look at the syntax, and then explore a real-world use case. ## Syntax @@ -46,7 +46,7 @@ Then after any changes, the `callback` is executed: changes are passed in the fi - `attributeName/attributeNamespace` -- the name/namespace (for XML) of the changed attribute, - `oldValue` -- the previous value, only for attribute or text changes, if the corresponding option is set `attributeOldValue`/`characterDataOldValue`. -For example, here's a `