diff --git a/Examples/Examples.csproj b/Examples/Examples.csproj
index d4ab282..f66914e 100644
--- a/Examples/Examples.csproj
+++ b/Examples/Examples.csproj
@@ -53,16 +53,16 @@
-
+
-
+
-
+
-
+
diff --git a/Examples/Web/README.md b/Examples/Web/README.md
index fae4651..50f8b15 100644
--- a/Examples/Web/README.md
+++ b/Examples/Web/README.md
@@ -12,7 +12,7 @@ The browser-wasm configuration only activates when publishing with
- .NET 10 SDK
- `dotnet workload install wasm-tools`
-- Raylib-cs (works with the local project, or nuget if MSBuild property `` is `true`
+- Raylib-cs (works with the local project, or nuget if MSBuild property `` is `true`
## Build
diff --git a/README.md b/README.md
index a27c3e1..9c9c4e8 100644
--- a/README.md
+++ b/README.md
@@ -117,17 +117,17 @@ dotnet test
Both projects can also consume the binding as a NuGet package but the in-repo version may not be published on
nuget.org yet. Pack it once into the local feed before the first build. Then to run against the Raylib-cs NuGet
package (the version set by `RaylibCsVersion` in [Directory.Build.props](Directory.Build.props)), set
-`UseRaylibCsPackage`:
+`RaylibCsForceLocalNuget`:
```sh
dotnet pack Raylib-cs -c Release -o nuget
dotnet build
```
```sh
-dotnet run --project Examples -p:UseRaylibCsPackage=true
+dotnet run --project Examples -p:RaylibCsForceLocalNuget=true
```
```sh
-dotnet test -p:UseRaylibCsPackage=true
+dotnet test -p:RaylibCsForceLocalNuget=true
```
Note that `NuGet.config` points restore at the local `./nuget` feed, so both projects pick up the freshly packed
diff --git a/Raylib-cs.Tests/Raylib-cs.Tests.csproj b/Raylib-cs.Tests/Raylib-cs.Tests.csproj
index 759930e..4f89cfd 100644
--- a/Raylib-cs.Tests/Raylib-cs.Tests.csproj
+++ b/Raylib-cs.Tests/Raylib-cs.Tests.csproj
@@ -15,13 +15,13 @@
-
+
-
+
-
+