From 2fbec213784e2f9a6e4b866b5d17c7f9956babe4 Mon Sep 17 00:00:00 2001
From: Maciek Sitkowski <58401630+sitek94@users.noreply.github.com>
Date: Sat, 8 Jun 2024 12:08:50 +0200
Subject: [PATCH] Fix typos in frontend questions about SSR (#5837)

---
 src/data/question-groups/frontend/content/ssr-when.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/data/question-groups/frontend/content/ssr-when.md b/src/data/question-groups/frontend/content/ssr-when.md
index de485ac0a..e77602977 100644
--- a/src/data/question-groups/frontend/content/ssr-when.md
+++ b/src/data/question-groups/frontend/content/ssr-when.md
@@ -2,6 +2,6 @@ Server-side rendering (SSR) is a technique in which a web server generates the H
 
 There are several ideal use cases for SSR:
 
-- **Content-rich websites**. For example, new sites, blogs, etc.
+- **Content-rich websites**. For example, news sites, blogs, etc.
 - **SEO-heavy applications**. When the success of the web app relies on SEO, this approach can greatly improve the performance of the site (and because of that, the SEO performance).
-- **Progressive web applications**. When the application needs to render fast to provide a fast and performance user experience, the application can initially be rendered in the server, and then hydrated in the client for subsequent integrations.
+- **Progressive web applications**. When the application needs to render fast to provide a fast and performance user experience, the application can initially be rendered on the server, and then hydrated on the client for subsequent integrations.