Replace/Remove mentions of NuCache

15/umbraco-cms/fundamentals/backoffice/settings-dashboards.md

@@ -12,7 +12,7 @@ The **Settings** section of the Umbraco backoffice has its own set of default da
 
 <summary>Welcome</summary>
 
-The Welcome dashboard is the first dashboard in the Settings section. Like all dashboards, it consists of a view that can be customized. The Welcome dashboard consists of links to different resources that can be used when developing your Umbraco website.
+The Welcome dashboard is the first dashboard in the Settings section. Like all dashboards, it has a customizable view and links to different resources for developing your Umbraco website.
 
 For more information about creating custom dashboards, see the [Dashboards](../../customizing/dashboards.md) article.
 
@@ -32,12 +32,16 @@ For more information about Examine Management, see the [Examine Management](../.
 
 <summary>Published Status</summary>
 
-The Published Status dashboard displays the status of your site in the Published Cache Status section alongside the Content and Media nodes value. The Caches section provides three options: Memory Cache, Database Cache, and Internals (NuCache).
+The Published Status dashboard displays the status of your site in the Published Cache Status section alongside the Content and Media nodes value. The Caches section provides three options: Memory Cache, Database Cache, and Internals.
 
 * Memory Cache - Reloads the in-memory cache by entirely reloading it from the database cache. Use it when you think that the memory cache has not been properly refreshed.
 * Database Cache - Rebuilds the database cache that is the content of the `cmsContentNu` table. Use it when reloading the Memory Cache is not enough and you think that the database cache has not been properly generated.
 * Internals - Lets you trigger a NuCache snapshots collection.
 
+{% hint style="info"%}
+As of Umbraco 15 `IPublishedSnapshot`, `IPublishedSnapshotAccessor` & `SnapshotCache` are all obsolete.
+{%endhint%}
+
 </details>
 
 <details>

15/umbraco-cms/fundamentals/code/source-control.md

@@ -38,7 +38,7 @@ appsettings-schema.json
 # Packages created from the backoffice (package.xml/package.zip)
 /umbraco/Data/CreatedPackages/
 
-# Temp folder containing Examine indexes, NuCache, MediaCache, etc.
+# Temp folder containing Examine indexes, MediaCache, etc.
 /umbraco/Data/TEMP/
 
 # SQLite database files

15/umbraco-cms/reference/configuration/README.md

@@ -116,6 +116,7 @@ To see what setting types you can access see the complete list below, each docum
 A complete list of all the configuration sections included in Umbraco, by default, can be seen here along with any keys they contain:
 
 * [Basic authentication settings](basicauthsettings.md)
+* [Cache settings](cache-settings.md)
 * [Connection strings settings](connectionstringssettings.md)
 * [Content settings](contentsettings.md)
 * [Debug settings](debugsettings.md)
@@ -130,7 +131,6 @@ A complete list of all the configuration sections included in Umbraco, by defaul
 * [Logging settings](loggingsettings.md)
 * [Maximum upload size settings](maximumuploadsizesettings.md)
 * [Models builder settings](modelsbuildersettings.md)
-* [NuCache settings](nucachesettings.md)
 * [Package migration settings](packagemigrationsettings.md)
 * [Plugins settings](pluginssettings.md)
 * [Request handler settings](requesthandlersettings.md)

15/umbraco-cms/reference/notifications/contentservice-notifications.md

@@ -217,8 +217,8 @@ Child scope will inherit the parent Scope's notification object which means if a
 
 **Why would one want to suppress events?**
 
-The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes.
+The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes.
 
-So if you did suppress events, it will require you to rebuild the NuCache and examine data manually.
+So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually.
 
 </details>

15/umbraco-cms/reference/notifications/hot-vs-cold-restarts.md

@@ -4,32 +4,32 @@ description: When rebooting an Umbraco CMS website it is common to distinguish b
 
 # Hot vs. cold restarts
 
-The load time of your site is dependent on a few different things. When talking about hot vs. cold restarts of your Umbraco CMS website it comes down to whether NuCache needs to be rebuilt.
+The load time of your site is dependent on a few different things. When talking about hot vs. cold restarts of your Umbraco CMS website it comes down to whether the search indexes need to be rebuilt.
 
-* **Cold restart**: When NuCache needs to rebuild.
-* **Hot start**: When NuCache does not need to rebuild.
+* **Cold restart**: When the search indexes need to rebuild.
+* **Hot start**: When the search indexes do not need to rebuild.
 
 ## Hot start
 
 When no cache needs to be rebuild, the restart of your site is generally faster. This is why it is referred to as a **hot restart**.
 
 ## Cold start
 
-The **cold restart** expression is generally used for when the NuCache needs to rebuild. This will resolve in a slower startup time, depending on the amount of content on the site. Generally speaking, the more content you have the longer a cold boot will take.
+The **cold restart** expression is generally used for when the search indexes need to rebuild. This will resolve in a slower startup time, depending on the amount of content on the site. Generally speaking, the more content you have the longer a cold boot will take.
 
 ## Troubleshooting slow startup
 
 Different things could be in play when your site is slow to startup after a reboot/restart.
 
 Below is a list of some of the more common reasons:
 
-* NuCache needs to rebuild (cold restart).
+* The search indexes need to rebuild (cold restart).
 * Examine indexes need to rebuild - for large sites, this can take some time.
 * The custom code on the website is not optimized and does not live up to .NET standards.
 
 ## In Memory Auto
 
-Another factor that can slow down time to first page load is the [In Memory Auto models builder](../templating/modelsbuilder/builder-modes.md#in-memory) setting. Having this setting enabled will result in the first page load being slower. The reason for this is that when the first page is requested, the strongly typed models needs to be compiled and loaded in. 
+Another factor that can slow down time to first page load is the [In Memory Auto models builder](../templating/modelsbuilder/builder-modes.md#in-memory) setting. Having this setting enabled will result in the first page load being slower. The reason for this is that when the first page is requested, the strongly typed models needs to be compiled and loaded in.
 
 This is, however, less noticeable on consecutive restarts, a bit like hot and cold restarts. Since the compiled models will be cached on disk, they don't need to be recompiled until the models change again.
 

15/umbraco-cms/reference/notifications/mediaservice-notifications.md

@@ -128,8 +128,8 @@ Child scope will inherit the parent Scope's notification object which means if a
 
 **Why would one want to suppress events?**
 
-The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes.
+The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes.
 
-So if you did suppress events, it will require you to rebuild the NuCache and examine data manually.
+So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually.
 
 </details>

15/umbraco-cms/reference/notifications/memberservice-notifications.md

@@ -69,8 +69,8 @@ Child scope will inherit the parent Scope's notification object which means if a
 
 **Why would one want to suppress events?**
 
-The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes.
+The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes.
 
-So if you did suppress events, it will require you to rebuild the NuCache and examine data manually.
+So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually.
 
 </details>