Fixed tag and props filename (#913)

WinUI2xVersion tag was wrong and also the props filename

---------

Co-authored-by: Jon Thysell (JAUNTY) <jthysell@microsoft.com>

.spelling

@@ -28,7 +28,7 @@ encodings
 enum
 exclusionList
 exe
-ExperimentalFlags.props
+ExperimentalFeatures.props
 filesystem
 flyout
 functor

docs/customizing-SDK-versions.md

@@ -42,16 +42,16 @@ However, C# apps restore NuGet packages to a location under your user profile, w
 
 C++ apps use `packages.config` to specify the set of NuGet packages, and then manually import the right `.props` and `.targets` files from the package.
 
-When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xPackageVersion` property).
+When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xVersion` property).
 
 For C++ apps, in addition to setting the property value, you will also need to modify the `packages.config` file which can be found next to the app project `.vcxproj` file, to point to the updated package version.
 
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
-```xml title="ExperimentalFlags.props"
+```xml title="ExperimentalFeatures.props"
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```

website/versioned_docs/version-0.64/customizing-SDK-versions.md

@@ -43,19 +43,19 @@ However, C# apps restore NuGet packages to a location under your user profile, w
 
 C++ apps use `packages.config` to specify the set of NuGet packages, and then manually import the right `.props` and `.targets` files from the package.
 
-When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xPackageVersion` property).
+When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xVersion` property).
 
 For C++ apps, in addition to setting the property value, you will also need to modify the `packages.config` file which can be found next to the app project `.vcxproj` file, to point to the updated package version.
 
 <!--DOCUSAURUS_CODE_TABS-->
 <!--C# app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
-```xml title="ExperimentalFlags.props"
+```xml title="ExperimentalFeatures.props"
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xPackageVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 
@@ -74,12 +74,12 @@ For C++ apps, in addition to setting the property value, you will also need to m
 
 <!--C++ app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
 ```xml
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xPackageVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 

website/versioned_docs/version-0.65/customizing-SDK-versions.md

@@ -43,19 +43,19 @@ However, C# apps restore NuGet packages to a location under your user profile, w
 
 C++ apps use `packages.config` to specify the set of NuGet packages, and then manually import the right `.props` and `.targets` files from the package.
 
-When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xPackageVersion` property).
+When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xVersion` property).
 
 For C++ apps, in addition to setting the property value, you will also need to modify the `packages.config` file which can be found next to the app project `.vcxproj` file, to point to the updated package version.
 
 <!--DOCUSAURUS_CODE_TABS-->
 <!--C# app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
-```xml title="ExperimentalFlags.props"
+```xml title="ExperimentalFeatures.props"
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xPackageVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 
@@ -74,12 +74,12 @@ For C++ apps, in addition to setting the property value, you will also need to m
 
 <!--C++ app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
 ```xml
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xPackageVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 

website/versioned_docs/version-0.67/customizing-SDK-versions.md

@@ -43,19 +43,19 @@ However, C# apps restore NuGet packages to a location under your user profile, w
 
 C++ apps use `packages.config` to specify the set of NuGet packages, and then manually import the right `.props` and `.targets` files from the package.
 
-When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xPackageVersion` property).
+When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xVersion` property).
 
 For C++ apps, in addition to setting the property value, you will also need to modify the `packages.config` file which can be found next to the app project `.vcxproj` file, to point to the updated package version.
 
 <!--DOCUSAURUS_CODE_TABS-->
 <!--C# app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
-```xml title="ExperimentalFlags.props"
+```xml title="ExperimentalFeatures.props"
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 
@@ -74,12 +74,12 @@ For C++ apps, in addition to setting the property value, you will also need to m
 
 <!--C++ app-->
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
 ```xml
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```
 

website/versioned_docs/version-0.68/customizing-SDK-versions.md

@@ -43,16 +43,16 @@ However, C# apps restore NuGet packages to a location under your user profile, w
 
 C++ apps use `packages.config` to specify the set of NuGet packages, and then manually import the right `.props` and `.targets` files from the package.
 
-When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xPackageVersion` property).
+When you create a C# or C++ React Native for Windows app, it is written in such a way that the WinUI version it uses is parametrized (i.e. it depends on the value of the `WinUI2xVersion` property).
 
 For C++ apps, in addition to setting the property value, you will also need to modify the `packages.config` file which can be found next to the app project `.vcxproj` file, to point to the updated package version.
 
 
-#### `windows\ExperimentalFlags.props`
+#### `windows\ExperimentalFeatures.props`
 
-```xml title="ExperimentalFlags.props"
+```xml title="ExperimentalFeatures.props"
 <PropertyGroup>
  <!-- other properties -->
- <WinUI2xVersion>2.6.0</WinUI2xPackageVersion>
+ <WinUI2xVersion>2.6.0</WinUI2xVersion>
 </PropertyGroup>
 ```