fix: MD047/single-trailing-newline (#2079)

Files should end with a single newline character

Author: nschonni

CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
 # Code of Conduct
 
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
-For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.

docs/android/get-started/index.md

@@ -46,4 +46,4 @@ development.
 
 > [!VIDEO https://youtube.com/embed/rkNikCa5D48]
 
-**Building Your First Android App with Xamarin for Visual Studio**
+**Building Your First Android App with Xamarin for Visual Studio**

docs/android/get-started/installation/android-emulator/hardware-acceleration.md

@@ -52,8 +52,8 @@ criteria are met:
     an **x86**-based virtual device.
 
 > [!IMPORTANT]
-> You can't run a VM-accelerated emulator inside another VM, such as 
-> a VM hosted by VirtualBox, VMWare, or Docker. You must run the Android 
+> You can't run a VM-accelerated emulator inside another VM, such as
+> a VM hosted by VirtualBox, VMWare, or Docker. You must run the Android
 > emulator [directly on your system hardware](https://developer.android.com/studio/run/emulator-acceleration.html#extensions).
 
 For information about launching and debugging with the Android
@@ -87,12 +87,12 @@ to support the Windows Hypervisor Platform:
 
 - Your computer must be updated to Windows 10 April 2018 update
     (build 1803) or later. You can verify that your Windows version
-    is up-to-date by using the following steps: 
+    is up-to-date by using the following steps:
 
-    1. Enter **About** in the Windows search box. 
-    2. Select **About your PC** in the search results. 
-    3. Scroll down in the **About** dialog to the **Windows specifications** 
-       section. 
+    1. Enter **About** in the Windows search box.
+    2. Select **About your PC** in the search results.
+    3. Scroll down in the **About** dialog to the **Windows specifications**
+       section.
     4. Verify that the **Version** is at least 1803:
 
         [![Windows specifications](hardware-acceleration-images/win/01-about-windows-w10-sml.png)](hardware-acceleration-images/win/01-about-windows-w10.png#lightbox)
@@ -220,7 +220,7 @@ accelerating the Android emulator:
    is a feature of macOS 10.10 and later that makes it possible to run
    virtual machines on a Mac.
 
-2. **Intel's Hardware Accelerated Execution Manager (HAXM)**. 
+2. **Intel's Hardware Accelerated Execution Manager (HAXM)**.
    [HAXM](https://software.intel.com/articles/intel-hardware-accelerated-execution-manager-intel-haxm)
    is a virtualization engine for computers running Intel CPUs.
 
@@ -237,10 +237,10 @@ if the following criteria are met:
     an **x86**-based virtual device.
 
 > [!IMPORTANT]
-> 
-> You can't run a  VM-accelerated emulator inside another VM, 
-> such as a VM  hosted by VirtualBox, VMWare, or Docker. You 
-> must run the Android emulator 
+>
+> You can't run a  VM-accelerated emulator inside another VM,
+> such as a VM  hosted by VirtualBox, VMWare, or Docker. You
+> must run the Android emulator
 > [directly on your system hardware](https://developer.android.com/studio/run/emulator-acceleration.html#extensions).
 
 For information about launching and debugging with the Android
@@ -251,7 +251,7 @@ emulator, see
 
 ## Accelerating with the Hypervisor Framework
 
-To use the Android emulator with the Hypervisor Framework, your Mac must 
+To use the Android emulator with the Hypervisor Framework, your Mac must
 meet the following criteria:
 
 - Your Mac must be running macOS 10.10 or later.
@@ -274,7 +274,7 @@ HAXM to accelerate the Android emulator (described next).
 
 If your Mac does not support the Hypervisor framework (or you are using
 a version of macOS earlier than 10.10), you can use **Intel's Hardware
-Accelerated Execution Manager** 
+Accelerated Execution Manager**
 ([HAXM](https://software.intel.com/articles/intel-hardware-accelerated-execution-manager-intel-haxm))
 to speed up the Android emulator.
 
@@ -343,4 +343,4 @@ guide.
 
 ## Related Links
 
-- [Run Apps on the Android Emulator](https://developer.android.com/studio/run/emulator)
+- [Run Apps on the Android Emulator](https://developer.android.com/studio/run/emulator)

docs/cross-platform/includes/development-environment.md

@@ -9,4 +9,4 @@ ms.topic: include
 |**Xamarin.Forms** ^|iOS & Android|Android, Windows/UWP (iOS with Mac computer)|
 |**Xamarin.Mac**|Yes|Open project & compile only|
 
-_^ [Other platforms](https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support) are also available._
+_^ [Other platforms](https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support) are also available._

docs/cross-platform/includes/install-xamarin-windows-2019.md

@@ -39,4 +39,4 @@ re-running the Visual Studio 2019 installer to modify workloads (see
 for details). Next, follow the steps listed above to install Xamarin.
 
 For more information about downloading and installing Visual Studio
-2019, see [Install Visual Studio 2019](https://docs.microsoft.com/visualstudio/install/install-visual-studio).
+2019, see [Install Visual Studio 2019](https://docs.microsoft.com/visualstudio/install/install-visual-studio).

docs/cross-platform/includes/install-xamarin-windows.md

@@ -47,4 +47,4 @@ re-running the Visual Studio 2017 installer to modify workloads (see
 for details). Next, follow the steps listed above to install Xamarin.
 
 For more information about downloading and installing Visual Studio
-2017, see [Install Visual Studio 2017](https://docs.microsoft.com/visualstudio/install/install-visual-studio).
+2017, see [Install Visual Studio 2017](https://docs.microsoft.com/visualstudio/install/install-visual-studio).

docs/cross-platform/troubleshooting/questions/nuget-packages-missing.md

@@ -10,23 +10,23 @@ ms.date: 05/08/2018
 
 # Missing packages error after updating Nuget packages
 
-This issue has mainly been reported on Xamarin.Forms sample app solutions, but the potential for this issue can happen on any project that uses NuGet packages. 
+This issue has mainly been reported on Xamarin.Forms sample app solutions, but the potential for this issue can happen on any project that uses NuGet packages.
 
 If after updating Nuget packages in your project or solution, you see an error that references the old package version numbers, such as:
 
 ```csharp
 Error: This project references NuGet package(s) that are missing on this computer.
-Enable NuGet Package Restore to download them.  
+Enable NuGet Package Restore to download them.
 For more information, see http://go.microsoft.com/fwlink/?LinkID=322105
 
 The missing file is ../../packages/Xamarin.Forms.1.3.1.6296/build/portable-win+net45+wp80+MonoAndroid10+MonoTouch10+Xamarin.iOS10/Xamarin.Forms.targets. (FormsGallery)
 ```
 
 In this example *Xamarin.Forms.1.3.1.6296* is the old version number that was removed with the Nuget package update.
 
-This can happen if the XML elements in the .csproj file that reference the old package version number had been manually added or edited, Nuget will not remove or update them if they had been manually added/edited, so the project is now looking for packages that have been deleted. 
+This can happen if the XML elements in the .csproj file that reference the old package version number had been manually added or edited, Nuget will not remove or update them if they had been manually added/edited, so the project is now looking for packages that have been deleted.
 
-To fix this issue,  manually edit the .csproj file(s) and delete all of the elements that reference the old version number. 
+To fix this issue,  manually edit the .csproj file(s) and delete all of the elements that reference the old version number.
 
 Sample elements to remove (if they have the old package version number):
 
@@ -37,4 +37,4 @@ Sample elements to remove (if they have the old package version number):
 
 <Import Project="..\..\packages\Xamarin.Forms.1.3.1.6296\build\portable-win+net45+wp80+MonoAndroid10+MonoTouch10+Xamarin.iOS10\Xamarin.Forms.targets" Condition="Exists('..\..\packages\Xamarin.Forms.1.3.1.6296\build\portable-win+net45+wp80+MonoAndroid10+MonoTouch10+Xamarin.iOS10\Xamarin.Forms.targets')" />
 <Error Condition="!Exists('..\..\packages\Xamarin.Forms.1.3.1.6296\build\portable-win+net45+wp80+MonoAndroid10+MonoTouch10+Xamarin.iOS10\Xamarin.Forms.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\..\packages\Xamarin.Forms.1.3.1.6296\build\portable-win+net45+wp80+MonoAndroid10+MonoTouch10+Xamarin.iOS10\Xamarin.Forms.targets'))" />
-```
+```

docs/cross-platform/troubleshooting/questions/visualstudio-2017-rc.md

@@ -9,6 +9,6 @@ ms.author: amburns
 ms.date: 03/29/2017
 ---
 
-Note to editors: This content has been intentionally deleted and redirected. 
+Note to editors: This content has been intentionally deleted and redirected.
 This redirect should be centralized with other redirects and this file should
-be removed.
+be removed.

docs/get-started/requirements.md

@@ -93,4 +93,4 @@ Xamarin.Forms solution at any time.
 These platforms are not supported when using Xamarin.Forms 3.0 or newer:
 
 - *Windows 8.1 / Windows Phone 8.1 WinRT*
-- *Windows Phone 8 Silverlight*
+- *Windows Phone 8 Silverlight*

docs/ios/platform/file-compression.md

@@ -81,4 +81,4 @@ static void CompressExample ()
 
 ## Async support
 
-The `CompressionStream` supports all the async operations that are supported by the `System.IO.DeflateStream`, which means that developers can use the async keyword to perform the compress/decompress operations without blocking the UI thread.
+The `CompressionStream` supports all the async operations that are supported by the `System.IO.DeflateStream`, which means that developers can use the async keyword to perform the compress/decompress operations without blocking the UI thread.

docs/ios/platform/gaming/scenekit.md

@@ -17,7 +17,7 @@ SceneKit is extremely easy to work with. It is a declarative API that takes care
 
 To work with SceneKit you create a scene graph using the `SCNScene` class. A scene contains a hierarchy of nodes, represented by instances of `SCNNode`, defining locations in 3D space. Each node has properties such as geometry, lighting and materials that affect its appearance, as illustrated by the following figure:
 
-![](scenekit-images/image7.png "The SceneKit hierarchy") 
+![](scenekit-images/image7.png "The SceneKit hierarchy")
 
 ## Create a Scene
 
@@ -68,7 +68,7 @@ scene.RootNode.AddChildNode (ambientLightNode);
 With the lights in place, the sphere is now visible in the scene.
 
 ![](scenekit-images/image8.png "The sphere is visible in the scene when lit")
- 
+
 ## Adding a Camera
 
 Adding a camera (SCNCamera) to the scene changes the point of view. The pattern to add the camera is similar. Create the camera, attach it to a node and add the node to the scene.
@@ -91,11 +91,11 @@ As you can see from the code above, SceneKit objects can be created using constr
 With the camera in place, the entire sphere is visible to the user:
 
 ![](scenekit-images/image9.png "The entire sphere is visible to the user")
- 
+
 You can add additional lights to the scene as well. Here is what it looks like with a few more omnidirectional lights:
 
 ![](scenekit-images/image10.png "The sphere with a few more omnidirectional lights")
- 
+
 Additionally, by setting `sceneView.AllowsCameraControl = true`, the user can change the point of view with a touch gesture.
 
 ### Materials
@@ -111,11 +111,11 @@ sphere.Materials = new SCNMaterial[] { material };
 This layers the image onto the node as shown below:
 
 ![](scenekit-images/image11.png "Layering the image onto the sphere")
- 
+
 A material can be set to respond to other types of lighting too. For example, the object can be made shiny and have its specular contents set to display specular reflection, resulting in a bright spot on the surface, as shown below:
 
 ![](scenekit-images/image12.png "The object made shiny with specular reflection, resulting in a bright spot on the surface")
- 
+
 Materials are very flexible, allowing you to achieve a lot with very little code. For example, instead of setting the image to the diffuse contents, set it to the reflective contents instead.
 
 ```csharp

docs/ios/platform/ios13/troubleshooting/index.md

@@ -51,4 +51,4 @@ Until there is a [fix](https://github.com/xamarin/xamarin-macios/issues/6216), t
 
    `/Applications/Xcode102.app/Contents/Developer/usr/bin/xcodebuild -runFirstLaunch`
 
-After following these steps, you should be able to work with the iOS simulator again.
+After following these steps, you should be able to work with the iOS simulator again.

docs/ios/tvos/platform/introduction-to-tvos12/index.md

@@ -64,4 +64,4 @@ to adopt Metal.
 - [tvOS Samples](https://docs.microsoft.com/samples/browse/?products=xamarin&term=Xamarin.iOS+tvOS)
 - [tvOS – Apple Developer (Apple)](https://developer.apple.com/tvos/)
 - [What's new in tvOS 12 (Apple) (video)](https://developer.apple.com/videos/play/wwdc2018/208/)
-- [TV (Apple)](https://www.apple.com/tv/)
+- [TV (Apple)](https://www.apple.com/tv/)

docs/tools/ios-simulator/deploy.md

@@ -14,4 +14,4 @@ Watch this video for step-by-step instructions on using Visual Studio 2017 on Wi
 
 > [!Video https://channel9.msdn.com/Shows/XamarinShow/Deploying--Debugging-NET-iOS-apps-with-Visual-Studio-2017/player]
 
-Learn more about the [Remoted iOS Simulators features](index.md).
+Learn more about the [Remoted iOS Simulators features](index.md).

docs/xamarin-forms/user-interface/toolbaritem.md

@@ -114,4 +114,4 @@ When the `Order` property is set to `Secondary`, behavior varies across platform
 
 * [ToolbarItem Demos](https://docs.microsoft.com/samples/xamarin/xamarin-forms-samples/userinterface-toolbaritem/)
 * [Images in Xamarin.Forms](~/xamarin-forms/user-interface/images.md)
-* [Xamarin.Forms MenuItem](~/xamarin-forms/user-interface/menuitem.md)
+* [Xamarin.Forms MenuItem](~/xamarin-forms/user-interface/menuitem.md)