diff --git a/doc/articles/uno-development/building-uno-ui.md b/doc/articles/uno-development/building-uno-ui.md
index fbb598f7fba9..c79b5b36da01 100644
--- a/doc/articles/uno-development/building-uno-ui.md
+++ b/doc/articles/uno-development/building-uno-ui.md
@@ -92,11 +92,11 @@ Here are some tips when building the Uno solution and failures happen:
 
 ### Building the reference assemblies for Skia and WebAssembly
 
-Skia and WebAssembly use a custom bait-and-switch technique for assemblies for which the `netstandard2.0` target framework assemblies (called reference assemblies) found in nuget packages (`lib` folder) are only used for building applications. At the end of a head build, those referene assemblies are replaced by public API compatible assemblies located in the `uno-runtime` folder of nuget packages.
+Skia and WebAssembly use a custom bait-and-switch technique for assemblies for which the `net7.0` and `netstandard2.0` target framework assemblies (called reference assemblies) found in nuget packages (`lib` folder) are only used for building applications. At the end of a head build, those referene assemblies are replaced by public API compatible assemblies located in the `uno-runtime\[target-framework]` folder of nuget packages.
 
 When developing a feature using solution filters, if new public APIs are added, building the Uno.UI solution will not update the reference assemblies, causing applications or libraries using the overriden nuget cache to be unable to use those newly added APIs.
 
-In order to update those reference assemblies, set `<UnoTargetFrameworkOverride>netstandard2.0</UnoTargetFrameworkOverride>`, then open either the android or iOS solution filters, then build the `Uno.UI` project (and only this one, the other projects in the solution will fail to build). Doing this will generate the proper assemblies with the new APIs to be used in application or libraries using the cache override.
+In order to update those reference assemblies, set `<UnoTargetFrameworkOverride>...</UnoTargetFrameworkOverride>` to `net7.0` or `netstandard2.0`, then open the `Uno.UI-Reference-Only.slnf` filter. You can now build the `Uno.UI` project. Doing this will generate the proper assemblies with the new APIs to be used in application or libraries using the nuget cache override.
 
 ### Using the Package Diff tool
 
diff --git a/doc/articles/uno-development/creating-ui-tests.md b/doc/articles/uno-development/creating-ui-tests.md
index 505478cc20e2..c868cff17a2b 100644
--- a/doc/articles/uno-development/creating-ui-tests.md
+++ b/doc/articles/uno-development/creating-ui-tests.md
@@ -17,7 +17,7 @@ UI tests contribute significantly to the CI build time, and for many purposes a
 ## Running UI tests locally
 
 1. Ensure [your environment is configured](../get-started-vs.md) for the platform you want to run on.
-1. Ensure `UnoTargetFrameworkOverride` is set to `MonoAndroid11.0` or `net6.0-android` for testing on Android, `xamarinios` or `net6.0-ios` for testing on iOS, and `netstandard2.0` for testing on Wasm.
+1. Ensure `UnoTargetFrameworkOverride` is set to `MonoAndroid11.0` or `net6.0-android` for testing on Android, `xamarinios` or `net6.0-ios` for testing on iOS, and `net7.0` or `netstandard2.0` for testing on Wasm.
 1. Open Uno.UI with the [correct target override and solution filter](building-uno-ui.md) for the platform you want to run on.
 1. [Build and run the SamplesApp](working-with-the-samples-apps.md) at least once.
 1. Only Android and WASM are supported from Visual Studio for Windows. (Running tests on iOS using a Mac is possible, see additional instructions below.)