update

docs/en/Community-Articles/2025-08-10-Using-Transfer-State-with-Angular-SSR/post.md

@@ -1,7 +0,0 @@
-# From Server to Browser — the Elegant Way: Angular TransferState Explained
-
-## Introduction
-
-When building Angular applications with Server-Side Rendering (SSR), one of the most common performance pitfalls is duplicated data fetching. Your server fetches data to render the initial HTML, and then — as soon as the browser bootstraps Angular — it fetches the same data all over again. That’s wasteful, especially for APIs that don’t change often.
-
-Enter TransferState, Angular’s elegant solution to bridge the data gap between the server and the browser. It allows you to transfer pre-fetched data from the server-rendered page to the client seamlessly — no redundant HTTP calls, no flickering spinners, and no extra waiting time.

docs/en/Community-Articles/2025-10-10-Using-Transfer-State-with-Angular-SSR/post.md

@@ -0,0 +1,6 @@
+# From Server to Browser — the Elegant Way: Angular TransferState Explained
+
+## Introduction
+
+When building Angular applications with Server-Side Rendering (SSR), one of the most common performance pitfalls is duplicated data fetching. Server fetch data while generating initial HTML, and then browser bootstraps Angular and it fetches the same data all over again. That’s wasteful, especially for APIs that don’t change often.
+To solve this problem, Angular provide **TransferState**. It allows to transfer data from application on server to application on browser, in this way you can avoid redundant unnecessary operations.