From 2978a3c1922d043942d1e52cddb60c83d0de7cd9 Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Sat, 3 Aug 2019 13:39:09 -0400 Subject: [PATCH] fix italicisation --- site/content/tutorial/15-context/01-context-api/text.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/tutorial/15-context/01-context-api/text.md b/site/content/tutorial/15-context/01-context-api/text.md index 32b0f2efcc..28001362f6 100644 --- a/site/content/tutorial/15-context/01-context-api/text.md +++ b/site/content/tutorial/15-context/01-context-api/text.md @@ -47,7 +47,7 @@ We can use anything as a key — we could do `setContext('mapbox', ...)` for exa ## Contexts vs. stores -Contexts and stores seem similar. They differ in that stores are available to *any* part of an app, while a context is only *available to a component and its descendants*. This can be helpful if you want to use several instances of a component without the state of one interfering with the state of the others. +Contexts and stores seem similar. They differ in that stores are available to *any* part of an app, while a context is only available to *a component and its descendants*. This can be helpful if you want to use several instances of a component without the state of one interfering with the state of the others. In fact, you might use the two together. Since context is not reactive, values that change over time should be represented as stores: