diff --git a/release-notes/9.0/preview/rc1/libraries.md b/release-notes/9.0/preview/rc1/libraries.md
index dcd6c747ac..0a1e2cea4d 100644
--- a/release-notes/9.0/preview/rc1/libraries.md
+++ b/release-notes/9.0/preview/rc1/libraries.md
@@ -17,7 +17,6 @@ Libraries updates in .NET 9 Release Candidate 1:
 
 * [Discussion](https://aka.ms/dotnet/9/rc1)
 * [Release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/README.md)
-* [Runtime release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/runtime.md)
 * [Libraries release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/libraries.md)
 
 ## WebSocket `Keep-Alive` Ping and Timeout
diff --git a/release-notes/9.0/preview/rc1/sdk.md b/release-notes/9.0/preview/rc1/sdk.md
index 1e4b91af88..c82c631e8a 100644
--- a/release-notes/9.0/preview/rc1/sdk.md
+++ b/release-notes/9.0/preview/rc1/sdk.md
@@ -4,7 +4,7 @@ Here's a summary of what's new in the .NET SDK in this release:
 
 * [Workload History](#workload-history)
 
-SDK updates in .NET 7 Release Candidate 1:
+SDK updates in .NET 9 Release Candidate 1:
 
 * [Release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/sdk.md)
 * [What's new in the .NET Runtime in .NET 9](https://learn.microsoft.com/dotnet/core/whats-new/dotnet-9/overview) documentation
@@ -13,7 +13,6 @@ SDK updates in .NET 7 Release Candidate 1:
 
 * [Discussion](https://aka.ms/dotnet/9/rc1)
 * [Release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/README.md)
-* [Runtime release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/runtime.md)
 * [Libraries release notes](https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/rc1/libraries.md)
 
 ## Feature
@@ -36,4 +35,4 @@ Id  Date                         Command       Workloads
 Running `dotnet workload history` will print out a table of the history of workload installations or modifications for the current .NET SDK installation. The table will show key information like the date of the installation or modification, the command that was run, the workloads that were installed or modified, and the relevant version(s) for the command.
 The most important piece of information is the _id_ - this can be used in the `dotnet workload update` command with the `--from-history` option (for example `dotnet workload update --from-history 3` to return to loose manifest mode) to tell the SDK to return to the state at that version. This can be useful if you want to revert to a previous state for any reason.
 
-In this example, I had an SDK installation with the initial state of the android, ios, maccatalyst, and maui-windows workloads installed. I then ran `dotnet workload install aspire --version 9.0.100-rc.1.24453.3` to install the aspire workload and switch to workload sets mode, and the history command shows that the installation was successful. If I want to return to the previous state for any reason, I can use the _id_ from the history table to do so: `dotnet workload update --from-history 1`.
\ No newline at end of file
+In this example, I had an SDK installation with the initial state of the android, ios, maccatalyst, and maui-windows workloads installed. I then ran `dotnet workload install aspire --version 9.0.100-rc.1.24453.3` to install the aspire workload and switch to workload sets mode, and the history command shows that the installation was successful. If I want to return to the previous state for any reason, I can use the _id_ from the history table to do so: `dotnet workload update --from-history 1`.