From fb6ea6067573e52428b7fb8a310f092d0d6917d9 Mon Sep 17 00:00:00 2001 From: Shubh Porwal Date: Wed, 14 Aug 2024 17:02:54 +0530 Subject: [PATCH 1/2] fix(docs): `instead` typo --- docs/framework/angular/devtools.md | 2 +- docs/framework/solid/devtools.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/framework/angular/devtools.md b/docs/framework/angular/devtools.md index 394522855d..00c1dcec73 100644 --- a/docs/framework/angular/devtools.md +++ b/docs/framework/angular/devtools.md @@ -62,4 +62,4 @@ import { Component } from '@angular/core'; - Use this to pass a nonce to the style tag that is added to the document head. This is useful if you are using a Content Security Policy (CSP) nonce to allow inline styles. - `shadowDOMTarget?: ShadowRoot` - Default behavior will apply the devtool's styles to the head tag within the DOM. - - Use this to pass a shadow DOM target to the devtools so that the styles will be applied within the shadow DOM instad of within the head tag in the light DOM. + - Use this to pass a shadow DOM target to the devtools so that the styles will be applied within the shadow DOM instead of within the head tag in the light DOM. diff --git a/docs/framework/solid/devtools.md b/docs/framework/solid/devtools.md index 530ccb81ee..4030f178d9 100644 --- a/docs/framework/solid/devtools.md +++ b/docs/framework/solid/devtools.md @@ -66,4 +66,4 @@ function App() { - Use this to pass a nonce to the style tag that is added to the document head. This is useful if you are using a Content Security Policy (CSP) nonce to allow inline styles. - `shadowDOMTarget?: ShadowRoot` - Default behavior will apply the devtool's styles to the head tag within the DOM. - - Use this to pass a shadow DOM target to the devtools so that the styles will be applied within the shadow DOM instad of within the head tag in the light DOM. + - Use this to pass a shadow DOM target to the devtools so that the styles will be applied within the shadow DOM instead of within the head tag in the light DOM. From 1c4c41519b4356a2bdfd794f74c1f1ad75704b6a Mon Sep 17 00:00:00 2001 From: Shubh Porwal Date: Wed, 14 Aug 2024 17:03:13 +0530 Subject: [PATCH 2/2] fix(docs): `optimizes` typo --- docs/framework/svelte/reactivity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/svelte/reactivity.md b/docs/framework/svelte/reactivity.md index af5e1e6dc9..8fdab9d13a 100644 --- a/docs/framework/svelte/reactivity.md +++ b/docs/framework/svelte/reactivity.md @@ -3,7 +3,7 @@ id: reactivity title: Reactivity --- -Svelte uses a compiler to build your code which optimises rendering. By default, components run once, unless they are referenced in your markup. To be able to react to changes in options you need to use [stores](https://svelte.dev/docs/svelte-store). +Svelte uses a compiler to build your code which optimizes rendering. By default, components run once, unless they are referenced in your markup. To be able to react to changes in options you need to use [stores](https://svelte.dev/docs/svelte-store). In the below example, the `refetchInterval` option is set from the variable `intervalMs`, which is bound to the input field. However, as the query is not able to react to changes in `intervalMs`, `refetchInterval` will not change when the input value changes.