Merge pull request #3723 from huypub/fix-blockquote-tag

remove blockquote tag

Author: alvinashcraft

uwp/app-resources/images-tailored-for-scale-theme-contrast.md

@@ -17,26 +17,26 @@ Some common qualifiers for images are [scale](tailor-resources-lang-scale-contra
 ## Qualify an image resource for scale, theme, and contrast
 The default value for the `scale` qualifier is `scale-100`. So, these two variants are equivalent (they both provide an image at scale 100, or scale factor 1).
 
-<blockquote>
+
 <pre>
 \Assets\Images\logo.png
 \Assets\Images\logo.scale-100.png
 </pre>
-</blockquote>
+
 
 
 You can use qualifiers in folder names instead of file names. That would be a better strategy if you have several asset files per qualifier. For purposes of illustration, these two variants are equivalent to the two above.
 
-<blockquote>
+
 <pre>
 \Assets\Images\logo.png
 \Assets\Images\scale-100\logo.png
 </pre>
-</blockquote>
+
 
 Next is an example of how you can provide variants of an image resource&mdash;named `/Assets/Images/logo.png`&mdash;for different settings of display scale, theme, and high contrast. This example uses folder naming.
 
-<blockquote>
+
 <pre>
 \Assets\Images\contrast-standard\theme-dark
 	\scale-100\logo.png
@@ -48,7 +48,7 @@ Next is an example of how you can provide variants of an image resource&mdash;na
 	\scale-100\logo.png
 	\scale-200\logo.png
 </pre>
-</blockquote>
+
 
 ## Reference an image or other asset from XAML markup and code
 The name&mdash;or identifier&mdash;of an image resource is its path and file name with any and all qualifiers removed. If you name folders and/or files as in any of the examples in the previous section, then you have a single image resource and its name (as an absolute path) is `/Assets/Images/logo.png`. Here’s how you use that name in XAML markup.
@@ -98,29 +98,29 @@ Also see [Tile and toast support for language, scale, and high contrast](/window
 ## Qualify an image resource for targetsize
 You can use the `scale` and `targetsize` qualifiers on different variants of the same image resource; but you can't use them both on a single variant of a resource. Also, you need to define at least one variant without a `TargetSize` qualifier. That variant must either define a value for `scale`, or let it default to `scale-100`. So, these two variants of the `/Assets/Square44x44Logo.png` resource are valid.
 
-<blockquote>
+
 <pre>
 \Assets\Square44x44Logo.scale-200.png
 \Assets\Square44x44Logo.targetsize-24.png
 </pre>
-</blockquote>
+
 
 And these two variants are valid. 
 
-<blockquote>
+
 <pre>
 \Assets\Square44x44Logo.png // defaults to scale-100
 \Assets\Square44x44Logo.targetsize-24.png
 </pre>
-</blockquote>
+
 
 But this variant is not valid.
 
-<blockquote>
+
 <pre>
 \Assets\Square44x44Logo.scale-200_targetsize-24.png
 </pre>
-</blockquote>
+
 
 ## Refer to an image file from your app package manifest
 If you name folders and/or files as in either of the two valid examples in the previous section, then you have a single app icon image resource and its name (as a relative path) is `Assets\Square44x44Logo.png`. In your app package manifest, simply refer to the resource by name. There's no need to use any URI scheme.

uwp/app-resources/makepri-exe-format-specific-indexers.md

@@ -278,14 +278,14 @@ The ResFiles indexer is identified by a `type` attribute of RESFILES. It indexes
 
 A `.resfiles` file is a text file containing a flat list of file paths. A `.resfiles` file can contain "//" comments. Here's an example.
 
-<blockquote>
+
 <pre>
 Strings\component1\fr\elements.resjson
 Images\logo.scale-100.png
 Images\logo.scale-140.png
 Images\logo.scale-180.png
 </pre>
-</blockquote>
+
 
 ## ResJSON
 

uwp/app-resources/uri-schemes.md

@@ -92,10 +92,8 @@ ms-appx:///images/logo.png
 
 The URI above may actually retrieve a file within the current app's package with the following physical file name.
 
-<blockquote>
 <pre>
 \Images\fr-FR\logo.scale-100_contrast-white.png
-</blockquote>
 </pre>
 
 You could of course also retrieve that same physical file by referring to it directly by its full name.

uwp/app-resources/using-mrt-for-converted-desktop-apps-and-games.md

@@ -523,7 +523,7 @@ would not map well to MRT. A better structure would be a `Resources` directory w
 For example, the application might have a set of custom UI commands (used for button labels etc.) in a simple text file named <span>ui.txt</span>, 
 laid out under a <span>UICommands</span> folder:
 
-<blockquote>
+
 <pre>
 + ProjectRoot
 |--+ Strings
@@ -539,22 +539,22 @@ laid out under a <span>UICommands</span> folder:
 |--- AppxManifest.xml
 |--- ...rest of project...
 </pre>
-</blockquote>
+
 
 #### Resource loading code
 
 This article assumes that at some point in your code you want to locate the file that contains a localized resource, load it, and then use it. The APIs used to load the resources, 
 the APIs used to extract the resources, etc. are not important. In pseudocode, there are basically three steps:
 
-<blockquote>
+
 <pre>
 set userLanguage = GetUsersPreferredLanguage()
 set resourceFile = FindResourceFileForLanguage(MY_RESOURCE_NAME, userLanguage)
 set resource = LoadResource(resourceFile) 
 
 // now use 'resource' however you want
 </pre>
-</blockquote>
+
 
 MRT only requires changing the first two steps in this process - how you determine the best candidate resources and how you locate them. It doesn't require you to change how you load 
 or use the resources (although it provides facilities for doing that if you want to take advantage of them).
@@ -578,7 +578,7 @@ this example, the file-based resources vs. the string resources)
 
 In pseudo-code, the way you would resolve a given resource file name (like `UICommands\ui.txt` in the sample above) is as follows:
 
-<blockquote>
+
 <pre>
 // Get the ResourceContext that applies to this app
 set resourceContext = ResourceContext.GetForViewIndependentUse()
@@ -598,7 +598,7 @@ set bestCandidate = desiredResource.Resolve(resourceContext)
 
 // Get the string value (the filename) from the ResourceCandidate
 set absoluteFileName = bestCandidate.ValueAsString
-</blockquote>
+
 </pre>
 
 Note in particular that the code does **not** request a specific language folder - like `UICommands\en-US\ui.txt` - even though that is how the files exist on-disk. Instead, it
@@ -618,7 +618,7 @@ user doesn't have the language listed in their preferences).
 
 For example, imagine a .NET application with the following layout, where all the files exist under the `MainApp` folder:
 
-<blockquote>
+
 <pre>
 + MainApp
 |--+ en-us
@@ -629,11 +629,11 @@ For example, imagine a .NET application with the following layout, where all the
 |  \--- MainApp.resources.dll
 \--- MainApp.exe
 </pre>
-</blockquote>
+
 
 After conversion to .appx, the layout will look something like this, assuming `en-US` was the default language and the user has both German and French listed in their language list:
 
-<blockquote>
+
 <pre>
 + WindowsAppsRoot
 |--+ MainApp_neutral
@@ -647,7 +647,7 @@ After conversion to .appx, the layout will look something like this, assuming `e
    \--+ fr-fr
       \--- <span>MainApp.resources.dll</span>
 </pre>
-</blockquote>
+
 
 Because the localized resources no longer exist in sub-directories underneath the main executable's install location, the built-in .NET resource resolution fails. Luckily, .NET has 
 a well-defined mechanism for handling failed assembly load attempts - the `AssemblyResolve` event. A .NET app using MRT must register for this event and provide the missing assembly