docs: fix typos and clarify root effect

Author: jnizet

adev/src/content/guide/signals/effect.md

@@ -19,7 +19,7 @@ Effects should be the last API you reach for. Always prefer `computed()` for der
 TIP: There are no situations where effect is good, only situations where it is appropriate.
 
 - Logging signal values, either for analytics or as a debugging tool.
-- Keeping data in sync with different kind of storges `window.localStorage`, session storage, cookies etc.
+- Keeping data in sync with different kind of storages: `window.localStorage`, session storage, cookies etc.
 - Adding custom DOM behavior that can't be expressed with template syntax.
 - Performing custom rendering to a `<canvas>` element, charting library, or other third party UI library.
 
@@ -68,11 +68,11 @@ export class EffectiveCounterComponent {
 Angular implicitly defines two implicit behaviors for its effects depending on the context they were created in.
 
 A "View Effect" is an `effect` created in the context of a component instantiation. This includes effects created by services that are tied to component injectors.<br>
-A "Root Effect" is created in a root provided service.
+A "Root Effect" is created in the context of a root provided service instantiation.
 
 The execution of both kind of `effect` are tied to the change detection process.
 
-- "View effects" are executed _before_ there corresponding compoent is checked the change detection process.
+- "View effects" are executed _before_ there corresponding component is checked the change detection process.
 - "Root effects" are executed prior to all components being checked by the change detection process.
 
 In both cases, if at least one of the effect dependency changed during the effect execution, the effect will re-run before moving ahead on the change detection process,
@@ -136,9 +136,9 @@ export class MyFancyChart {
 }
 ```
 
-In this example `afterRenderEffect` to update a chart created by a 3rd party library.
+In this example `afterRenderEffect` is used to update a chart created by a 3rd party library.
 
-TIP: You often don't need `afterRenderEffect` to check for DOM changes. APIs like `ResizeObserver`, `MutationObserver` and `IntersectionObserver` are preferred to `effect` or afterRenderEffect when possible.
+TIP: You often don't need `afterRenderEffect` to check for DOM changes. APIs like `ResizeObserver`, `MutationObserver` and `IntersectionObserver` are preferred to `effect` or `afterRenderEffect` when possible.
 
 ### Render phases