From 4e85482cab64739231d06940c6bb1cd3ed57a4a3 Mon Sep 17 00:00:00 2001 From: ndaemy Date: Fri, 11 Jul 2025 01:32:08 +0900 Subject: [PATCH] fix: broken line breaks in step-by-step file --- .../docs/cms/migration/v4-to-v5/step-by-step.md | 11 ++++------- docusaurus/static/llms-full.txt | 11 ++++------- 2 files changed, 8 insertions(+), 14 deletions(-) diff --git a/docusaurus/docs/cms/migration/v4-to-v5/step-by-step.md b/docusaurus/docs/cms/migration/v4-to-v5/step-by-step.md index 66fd42c6a1..aae6bae26f 100644 --- a/docusaurus/docs/cms/migration/v4-to-v5/step-by-step.md +++ b/docusaurus/docs/cms/migration/v4-to-v5/step-by-step.md @@ -25,13 +25,10 @@ Your Strapi v4 application is already running on the latest v4 minor and patch v Before getting into the upgrade process itself, take the following precautions: -1. **Backup your database**. - - If you are using SQLite with the default configuration (the default database provided with Strapi), your database file is named `data.db` and is located in the `.tmp/` folder at the root of your Strapi application. - - If you are using another type of database, please refer to their official documentation (see and ). - - If your project is hosted on Strapi Cloud, you can manually [create a backup](/cloud/projects/settings#creating-a-manual-backup). +1. **Backup your database**: + * If you are using SQLite with the default configuration (the default database provided with Strapi), your database file is named `data.db` and is located in the `.tmp/` folder at the root of your Strapi application. + * If you are using another type of database, please refer to their official documentation (see and ). + * If your project is hosted on Strapi Cloud, you can manually [create a backup](/cloud/projects/settings#creating-a-manual-backup). 2. **Backup your code**: * If your code is versioned with git, create a new dedicated branch to run the migration. * If your code is _not_ versioned with git, create a backup of your working Strapi v4 code and store it in a safe place. diff --git a/docusaurus/static/llms-full.txt b/docusaurus/static/llms-full.txt index 477f7eeae9..5b38608ab5 100644 --- a/docusaurus/static/llms-full.txt +++ b/docusaurus/static/llms-full.txt @@ -8937,13 +8937,10 @@ Your Strapi v4 application is already running on the latest v4 minor and patch v Before getting into the upgrade process itself, take the following precautions: -1. **Backup your database**. - - If you are using SQLite with the default configuration (the default database provided with Strapi), your database file is named `data.db` and is located in the `.tmp/` folder at the root of your Strapi application. - - If you are using another type of database, please refer to their official documentation (see and ). - - If your project is hosted on Strapi Cloud, you can manually [create a backup](/cloud/projects/settings#creating-a-manual-backup). +1. **Backup your database**: + * If you are using SQLite with the default configuration (the default database provided with Strapi), your database file is named `data.db` and is located in the `.tmp/` folder at the root of your Strapi application. + * If you are using another type of database, please refer to their official documentation (see and ). + * If your project is hosted on Strapi Cloud, you can manually [create a backup](/cloud/projects/settings#creating-a-manual-backup). 2. **Backup your code**: * If your code is versioned with git, create a new dedicated branch to run the migration. * If your code is _not_ versioned with git, create a backup of your working Strapi v4 code and store it in a safe place.