Skip to content

Commit f196a38

Browse files
committed
chore: correct typos and PR suggestions
1 parent 628a38f commit f196a38

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/advanced/performance.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ You can do that by setting the `renderMode` prop to `on-demand` or `manual`:
3232

3333
#### Automatic Invalidation
3434

35-
When using `render-mode="on-demand"`, Tres.js will automatically invalidate the current frame by observing component props and lyfecycle hooks like `onMounted` and `onUnmounted`. It will also invalidate the frame when resizing the window or change any prop from the `<TresCanvas>` component like `clearColor` or `antialias`.
35+
When using `render-mode="on-demand"`, Tres.js will automatically invalidate the current frame by observing component props and lifecycle hooks like `onMounted` and `onUnmounted`. It will also invalidate the frame when resizing the window or changing any prop from the `<TresCanvas>` component like `clearColor` or `antialias`.
3636

37-
This will trigger a new render:
37+
The code below updates TresMesh's position-x prop every second, triggering a new render.
3838

3939
```vue
4040
<script setup>
@@ -59,7 +59,7 @@ setTimeout(() => {
5959

6060
#### Manual Invalidation
6161

62-
Since is not really possible to observe all the possible changes in your application, you can also manually invalidate the frame by calling the `invalidate()` method from the [`useTresContext` composable](../api/composables.md#usetrescontext):
62+
Since it is not really possible to observe all the possible changes in your application, you can also manually invalidate the frame by calling the `invalidate()` method from the [`useTresContext` composable](../api/composables.md#usetrescontext):
6363

6464

6565
::: code-group

0 commit comments

Comments
 (0)