Fix broken image in Using Visual Studio Editor Package page

Author: chrstphrsxtn

.gitattributes

@@ -3,3 +3,4 @@
 # Denote all files that are truly binary and should not be mergeable.
 *.dll binary
 *.exe binary
+*.png binary

Packages/com.unity.ide.visualstudio/Documentation~/Images/external-tools-tab.png

@@ -2,7 +2,7 @@
 
 To use the package, go to **Edit** > **Preferences** > **External Tools** > **External Script Editor** and select the version of **Visual Studio** you have installed. When you select this option, the window reloads and displays settings that control production of .csproj files.
 
-![External Tools tab in the Preferences window](Images/external-tools-tab.png)
+![External Tools tab in the Preferences window](Images/vs-external-tools.png)
 
 ## Generate .csproj files
 
@@ -20,4 +20,4 @@ These settings control whether to generate .csproj files for any installed packa
 |       **Built-in packages** | Any package that is already installed as part of the default Unity installation. |
 |       **Tarball packages** | Any package you install from a GZip tarball archive on the local machine, outside of your Unity project. |
 |       **Unknown packages** | Any package which Unity cannot determine an origin for. This could be because the package doesn’t list its origin, or that Unity doesn’t recognize the origin listed. |
-|       **Player projects** | For each player project, generate an additional .csproj file named ‘originalProjectName.Player.csproj’. This allows different project types to have their code included in Visual Studio’s systems, such as assembly definitions or testing suites. |
+|       **Player projects** | For each player project, generate an additional .csproj file named ‘originalProjectName.Player.csproj’. This allows different project types to have their code included in Visual Studio’s systems, such as assembly definitions or testing suites. |