From 60f51ec92934b47c729331b2a87012adf71d5bb7 Mon Sep 17 00:00:00 2001 From: Shu Uesugi Date: Thu, 16 Apr 2020 16:34:20 -0700 Subject: [PATCH] Simplify language --- api-routes-starter/posts/ssg-ssr.md | 2 +- basics-final/posts/ssg-ssr.md | 2 +- dynamic-routes-starter/posts/ssg-ssr.md | 2 +- typescript-final/posts/ssg-ssr.md | 2 +- typescript-starter/posts/ssg-ssr.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/api-routes-starter/posts/ssg-ssr.md b/api-routes-starter/posts/ssg-ssr.md index 9883b32..fe4a156 100644 --- a/api-routes-starter/posts/ssg-ssr.md +++ b/api-routes-starter/posts/ssg-ssr.md @@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request. -In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data. \ No newline at end of file +In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data. \ No newline at end of file diff --git a/basics-final/posts/ssg-ssr.md b/basics-final/posts/ssg-ssr.md index 9883b32..fe4a156 100644 --- a/basics-final/posts/ssg-ssr.md +++ b/basics-final/posts/ssg-ssr.md @@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request. -In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data. \ No newline at end of file +In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data. \ No newline at end of file diff --git a/dynamic-routes-starter/posts/ssg-ssr.md b/dynamic-routes-starter/posts/ssg-ssr.md index 9883b32..fe4a156 100644 --- a/dynamic-routes-starter/posts/ssg-ssr.md +++ b/dynamic-routes-starter/posts/ssg-ssr.md @@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request. -In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data. \ No newline at end of file +In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data. \ No newline at end of file diff --git a/typescript-final/posts/ssg-ssr.md b/typescript-final/posts/ssg-ssr.md index 9883b32..fe4a156 100644 --- a/typescript-final/posts/ssg-ssr.md +++ b/typescript-final/posts/ssg-ssr.md @@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request. -In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data. \ No newline at end of file +In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data. \ No newline at end of file diff --git a/typescript-starter/posts/ssg-ssr.md b/typescript-starter/posts/ssg-ssr.md index 9883b32..fe4a156 100644 --- a/typescript-starter/posts/ssg-ssr.md +++ b/typescript-starter/posts/ssg-ssr.md @@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request. -In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data. \ No newline at end of file +In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data. \ No newline at end of file