Merge branch 'next' of github.com:strapi/documentation into next

Author: pwizla

docusaurus/docs/cloud/getting-started/caching.md

@@ -4,25 +4,19 @@ displayed_sidebar: cloudSidebar
 sidebar_position: 4
 tags:
 - caching
-- Content Delivery Network (CDN) caching
+- Content Delivery Network (CDN)
 - Strapi Cloud
 ---
 
-import NotV5 from '/docs/snippets/_not-updated-to-v5.md'
-
 # Caching & Performance
 
-<NotV5/>
-
 For Strapi Cloud applications with large amounts of cacheable content, such as images, videos, and other static assets, enabling CDN (Content Delivery Network) caching via the [`Cache-control` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control) can help improve application performance.
 
 CDN caching can help improve application performance in a few ways:
 
 * **Reducing Latency**: Caching frequently accessed content on edge servers located closer to the end-users can reduce the time it takes to load content.
 * **Offloading Origin Server**: By caching content on edge servers it can offload the origin server, reducing the load and allowing it to focus on delivering more dynamic content.
 * **Handling Traffic Spikes**: Help handle traffic spikes by distributing the load across multiple edge servers. This can prevent the origin server from becoming overwhelmed during peak traffic times and ensures a consistent user experience.
-* **Minimizing Round-Trips**: By serving content directly from the edge servers, this can reduce the time it takes to load content.
-* **Improving Scalability**: Distributing content across multiple edge servers can improve scalability, making the application more reliable and responsive.
 
 ## Cache-Control Header in Strapi Cloud
 

docusaurus/docs/dev-docs/migration/v4-to-v5/breaking-changes/attributes-and-content-types-names-reserved.md

@@ -42,7 +42,9 @@ The following attribute names can be created on a content type:
 - `localizations`
 - `strapi_assignee`
 - `strapi_stage`
-- anything with the prefix `strapi`
+- `then`
+- `document`
+- anything with the prefix `strapi`, `_strapi`, or `__strapi`
 
 Any model name can be prefixed with `strapi`.
 
@@ -62,9 +64,11 @@ The following attribute names can **not** be created on a content type:
 - `localizations`
 - `strapi_assignee`
 - `strapi_stage`
-- `anything` with the prefix `strapi` or `__strapi`
+- `then`
+- `document`
+- anything with the prefix `strapi`, `_strapi`, or `__strapi`
 
-Model names can **not** be prefixed with `strapi` or `__strapi`.
+Model names can **not** be prefixed with `strapi`, `_strapi`, or `__strapi`.
 
 </SideBySideColumn>
 

docusaurus/docs/dev-docs/migration/v4-to-v5/breaking-changes/server-default-log-level.md

@@ -52,6 +52,8 @@ The log level defaults to `http`. This means that `silly`and `debug` level logs
 
 The log level can be configured either in the `server.js` file as described in the following Manual migration section, or as described in the [middlewares configuration](/dev-docs/configurations/middlewares#logger) documentation.
 
+[See the list of Winston log levels](https://www.npmjs.com/package/winston#logging-levels).
+
 ### Manual migration
 
 To migrate to Strapi 5: