Improve generic references to package/assembly

Author: Kraig Brockschmidt

docs/Guides/Create-UWP-Controls.md

@@ -66,14 +66,14 @@ The structure of the file is as follows:
 
 where:
 
-- *your_package_file*: the name of your control file, such as `ManagedPackage.winmd`.
+- *your_package_file*: the name of your control file, such as `ManagedPackage.winmd` ("ManagedPackage" is an arbitrary named used for this example and has no other meaning).
 - *vs_category*: The label for the group in which the control should appear in the Visual Studio designer’s toolbox. A `VSCategory` is necessary for the control to appear in the toolbox.
 - *blend_category*: The label for the group in which the control should appear in the Blend designer’s Assets pane. A `BlendCategory` is necessary for the control to appear in Assets.
 - *type_full_name_n*: The fully-qualified name for each control, including the namespace, such as `ManagedPackage.MyCustomControl`. Note that the dot format is used for both managed and native types.
 
 In more advanced scenarios, you can also include multiple `<File>` elements within `<FileList>` when a single package contains multiple control assemblies. You can also have multiple `<ToolboxItems>` nodes within a single `<File>` if you want to organize your controls into separate categories.
 
-In the following example, the control implemented in `ManagedPackage.winmd` will appear in Visual Studio and Blend in a group named “Managed Package”, and “MyCustomControl” will appear in that group.
+In the following example, the control implemented in `ManagedPackage.winmd` will appear in Visual Studio and Blend in a group named “Managed Package”, and “MyCustomControl” will appear in that group. All these names are arbitrary.
 
 ```xml
 <FileList>
@@ -143,12 +143,12 @@ For example, let’s say you’ve set the TPMinV for you controls package to Win
 \ref\uap10.0\*
 ```
 
-To enforce the appropriate TPMinV check, create an [MSBuild targets file](https://docs.microsoft.com/visualstudio/msbuild/msbuild-targets) and package it under the build folder:
+To enforce the appropriate TPMinV check, create an [MSBuild targets file](https://docs.microsoft.com/visualstudio/msbuild/msbuild-targets) and package it under the build folder (replacing "your_assembly_name" with the name of your specific assembly):
 
 ```
 \build
 	\uap10.0
-		MyManagedPackage.targets
+		your_assembly_name.targets
 \lib
 \tools
 ```
@@ -174,15 +174,16 @@ Here is an example of what the targets file should look like:
 
 ## Add design-time support
 
-To configure where the control properties show up in the property inspector, add custom adorners, etc., place your `design.dll` file inside the `lib\<platform>\Design` folder as appropriate to the target platform:
+To configure where the control properties show up in the property inspector, add custom adorners, etc., place your `design.dll` file inside the `lib\<platform>\Design` folder as appropriate to the target platform. Also, to ensure that the **[Edit Template > Edit a Copy](https://docs.microsoft.com/windows/uwp/controls-and-patterns/xaml-styles#modify-the-default-system-styles)** feature works, you must include the `Generic.xaml` and any resource dictionaries that it merges in the `<AssemblyName>\Themes` folder. (This file has no impact on the runtime behavior of a control.)
+
 
 ```
 \build
 \lib
 	\uap10.0.14393.0
 		\Design
 			\MyControl.design.dll
-		\ManagedPackage
+		\your_assembly_name
 			\Themes		
 				Generic.xaml
 \tools
@@ -191,7 +192,6 @@ To configure where the control properties show up in the property inspector, add
 > [!Note]
 > By default, control properties will show up under the Miscellaneous category in the property inspector.
 
-To ensure that the **[Edit Template > Edit a Copy](https://docs.microsoft.com/windows/uwp/controls-and-patterns/xaml-styles#modify-the-default-system-styles)** feature works, you must include the `Generic.xaml` and any resource dictionaries that it merges in the `<AssemblyName>\Themes` folder.
 
 ## Use strings and resources
 
@@ -201,14 +201,14 @@ For an example, refer to [MyCustomControl.cs](https://github.com/NuGet/Samples/b
 
 ## Package content such as images
 
-To package content such as images that can be used by your control or the consuming UWP project. add those files `lib\uap10.0.14393.0` folder as follows:
+To package content such as images that can be used by your control or the consuming UWP project. add those files `lib\uap10.0.14393.0` folder as follows ("your_assembly_name" should again match your particular control):
 
 ```
 \build
 \lib
 	\uap10.0.14393.0
 		\Design
-		\ManagedPackage
+		\your_assembly_name
 \contosoSampleImage.jpg
 \tools
 ```