+
+
+
+
+
+
+
+
+ @if (!isUwu) {
+
+ } @else {
+ 
+ }
+
+
+ }
+
+
+
+
+
+
+
+
+ Trabaja a cualquier escala
++ Angular te permite empezar poco a poco en un camino bien iluminado y + te apoya a medida que tu equipo y tus aplicaciones crecen. +
+
+
+
+
+
+
+
+
+ Amado por millones
++ Únete a los millones de desarrolladores de todo el mundo que + construyen con Angular en una comunidad próspera y amigable. +
+
+
+
+
+
+
+
+
+
+
+ + Construir para todos + +
++ Confía en el soporte integrado de hidratación, internacionalización, + seguridad y accesibilidad de Angular para construir para todos en + todo el mundo. +
+
+
+
+
+
+
+
+ @defer (on viewport(buildForEveryone); prefetch on
+ viewport(lovedByMillions)) {
+ ![Code editor]()
+ }
+
+ 
-
```mermaid
graph TD;
app[AppComponent] --- header[HeaderComponent];
diff --git a/adev-es/src/content/best-practices/runtime-performance/slow-computations.md b/adev-es/src/content/best-practices/runtime-performance/slow-computations.md
index e079717..38f8aab 100644
--- a/adev-es/src/content/best-practices/runtime-performance/slow-computations.md
+++ b/adev-es/src/content/best-practices/runtime-performance/slow-computations.md
@@ -19,7 +19,7 @@ For example, in the preceding screenshot, the second recorded change detection c
Here are several techniques to remove slow computations:
* **Optimizing the underlying algorithm**. This is the recommended approach. If you can speed up the algorithm that is causing the problem, you can speed up the entire change detection mechanism.
-* **Caching using pure pipes**. You can move the heavy computation to a pure [pipe](/guide/pipes). Angular reevaluates a pure pipe only if it detects that its inputs have changed, compared to the previous time Angular called it.
+* **Caching using pure pipes**. You can move the heavy computation to a pure [pipe](guide/pipes). Angular reevaluates a pure pipe only if it detects that its inputs have changed, compared to the previous time Angular called it.
* **Using memoization**. [Memoization](https://en.wikipedia.org/wiki/Memoization) is a similar technique to pure pipes, with the difference that pure pipes preserve only the last result from the computation where memoization could store multiple results.
* **Avoid repaints/reflows in lifecycle hooks**. Certain [operations](https://web.dev/avoid-large-complex-layouts-and-layout-thrashing/) cause the browser to either synchronously recalculate the layout of the page or re-render it. Since reflows and repaints are generally slow, you want to avoid performing them in every change detection cycle.
diff --git a/adev-es/src/content/best-practices/runtime-performance/zone-pollution.md b/adev-es/src/content/best-practices/runtime-performance/zone-pollution.md
index 8e7326d..27b22fc 100644
--- a/adev-es/src/content/best-practices/runtime-performance/zone-pollution.md
+++ b/adev-es/src/content/best-practices/runtime-performance/zone-pollution.md
@@ -35,7 +35,7 @@ class AppComponent implements OnInit {
The preceding snippet instructs Angular to call `setInterval` outside the Angular Zone and skip running change detection after `pollForUpdates` runs.
-Third-party libraries commonly trigger unnecessary change detection cycles because they weren't authored with Zone.js in mind. Avoid these extra cycles by calling library APIs outside the Angular zone:
+Third-party libraries commonly trigger unnecessary change detection cycles when their APIs are invoked within the Angular zone. This phenomenon particularly affects libraries that setup event listeners or initiate other tasks (such as timers, XHR requests, etc.). Avoid these extra cycles by calling library APIs outside the Angular zone: