Skip to content

Commit 87d0340

Browse files
authored
fix: big-signal-md typos (tomalaforge#1000)
1 parent fbb6932 commit 87d0340

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/src/content/docs/challenges/signal/53-big-signal-performance.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Challenge 53 is about performance while using big signal object
44
author: thomas-laforge
55
contributors:
66
- tomalaforge
7+
- jdegand
78
challengeNumber: 53
89
command: signal-big-signal-performance
910
sidebar:
@@ -13,11 +14,12 @@ sidebar:
1314

1415
## Information
1516

16-
In this challenge, you can imagine a big application where you store your user state inside a service and you use this service to use your user anywhere in your application.
17-
The issue is when you update one property of your user, the entire application is updating.
17+
For this challenge, you can imagine a large-scale application where you use a service to save and retrieve your user state at any time within the application.
1818

19-
I added the `CDFlashingDirective` to vizualise when one component is rerendering.
19+
The problem is that updating a single user property updates the entire application.
20+
21+
I added the `CDFlashingDirective` to visualize when one component is rendering.
2022

2123
## Statement
2224

23-
With Signal, you can now be more fine-grained in what the UI is rerendering. The goal of this challenge is to understand why everything is rerendering and you refactor the application to be more performante.
25+
With signals, you can now be more fine-grained in what the UI is rendering. The goal of this challenge is to understand why everything is re-rendering and to refactor the application to be more performant.

0 commit comments

Comments
 (0)