Merge pull request #921 from PlayEveryWare/fix/doc-links

paulhazen · web-flow · commit 330be9af9544 · 2024-09-20T12:40:12.000-07:00
Fix Documentation Links
diff --git a/.github/README.md b/.github/README.md
@@ -1,4 +1,4 @@
-<a href="/readme.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
 
 <div align="center"> <img src="/com.playeveryware.eos/Documentation~/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
 
diff --git a/com.playeveryware.eos/Documentation~/android/README_Android.md b/com.playeveryware.eos/Documentation~/android/README_Android.md
@@ -1,6 +1,6 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
 
-<div align="center"> <img src="/docs/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
+<div align="center"> <img src="/com.playeveryware.eos/Documentation~/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
 
 # <div align="center">Android</div>
 ---
@@ -52,7 +52,7 @@ You can follow the standard <a href="/README.md#configuring-the-plugin">Configur
 
 3. Update the <a href="https://docs.unity3d.com/2021.3/Documentation/Manual/class-PlayerSettingsAndroid.html">Minimum API Level</a> to be at least ```Android 6.0 'Marshmallow' (API Level 23)```.
 
-4. Optionally, set the plugin to <a href="/docs/android/link_eos_library_settings.md">link the EOS Library dynamically</a>.
+4. Optionally, set the plugin to <a href="link_eos_library_settings.md">link the EOS Library dynamically</a>.
 
 
 # FAQ
diff --git a/com.playeveryware.eos/Documentation~/android/environment_setup_android.md b/com.playeveryware.eos/Documentation~/android/environment_setup_android.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
 
 # <div align="center">Environment Setup for Android</div>
 ---
@@ -9,7 +9,7 @@
 
 2. Open the "Add modules" window.
 
-    <img src="/docs/images/unity_add_modules.png" width="500" />
+    <img src="/com.playeveryware.eos/Documentation~/images/unity_add_modules.png" width="500" />
 
 2. Select and install the following modules:
 
@@ -30,7 +30,7 @@ The following methods will show how to install the missing build-tool 30.0.3, an
 1. [Install Android Studio](https://developer.android.com/studio)
 2. Run the SDK Manager
 
-    <img src="/docs/images/android_studio_sdk_manager.png" width="500" />
+    <img src="/com.playeveryware.eos/Documentation~/images/android_studio_sdk_manager.png" width="500" />
 
 ### Manage SDK through command prompt
 
diff --git a/com.playeveryware.eos/Documentation~/android/link_eos_library_settings.md b/com.playeveryware.eos/Documentation~/android/link_eos_library_settings.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
 
 # <div align="center">Linking EOS Library on Android Settings</div>
 ---
diff --git a/com.playeveryware.eos/Documentation~/contributions.md b/com.playeveryware.eos/Documentation~/contributions.md
@@ -61,7 +61,7 @@ See [standards.md](/com.playeveryware.eos/Documentation~/standards.md).
 
 ## Unit Testing
 
-See [our documentation on unit testing](/com.playeveryware.eos/Documentation~/unit-testing.md).
+See [our documentation on unit testing](/com.playeveryware.eos/Documentation~/unit_testing.md).
 
 ## Core Classes
 
diff --git a/com.playeveryware.eos/Documentation~/dev_env/HyperV_Linux_Guest_VM.md b/com.playeveryware.eos/Documentation~/dev_env/HyperV_Linux_Guest_VM.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 # <div align="center">Setting up a Hyper-V Linux Guest VM</div>
 ---
@@ -14,17 +14,17 @@ This document describes how to create a Ubuntu Virtual Machine on Hyper-V suitab
     > [!NOTE] 
     > The follow screenshots are taken in Windows 11, so if you are running Windows 10 yours might look a little differently.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/windows-features-search.png" width="350" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/windows-features-search.png" width="350" />
 
 2. Make sure you select all of the options below.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/windows-features-on-off.png" width="400" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/windows-features-on-off.png" width="400" />
 
     If these options are greyed out, you may need to enter your bios settings to enable virtualization. See the following guide for general instructions on how to accomplish this: [How to Enable CPU Virtualization in Your Computer BIOS](https://www.bleepingcomputer.com/tutorials/how-to-enable-cpu-virtualization-in-your-computer-bios/).
 
     You can also tell if Virtualization is enabled in your BIOS by looking at the CPU Performance tab in Task Manager.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/task-manager-virtualization-check.png" width="500" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/task-manager-virtualization-check.png" width="500" />
 
     If it says "Disabled" instead of "Enabled," (like it does here) you will need to enable it in your BIOS.
 
@@ -36,14 +36,14 @@ Setting up network configuration can be a little bit confusing if you're doing i
 
 1. After restarting your computer, open the Hyper-V Manager, and configure the network by opening the "Virtual Switch Manager..." in the right-hand "Actions" bar.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/virtual-switch-manager.png" width="150" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/virtual-switch-manager.png" width="150" />
 
 2. If there _isn't_ **already** a "Default Switch" listed in the Virtual Switch Manager, go ahead and select "External," and "Create Virtual Switch," naming the switch "Default Switch."
 
     > [!NOTE]
     > Make sure to check "Allow management operating system to share this network adapter."
 
-    <img src="/docs/images/hyperv_linux_guest_vm/external-network.png" width="175" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/external-network.png" width="175" />
 
     When it's done it should look like this:
 
@@ -55,33 +55,33 @@ The "Enhanced Session" feature of Hyper-V doesn't play very nicely with Ubuntu,
 
 Go to Hyper-V Manager Actions bar and select "Hyper-V Settings..." and disable the "Use enhanced session mode."
 
-<img src="/docs/images/hyperv_linux_guest_vm/enhanced-session.png" width="520" />
+<img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/enhanced-session.png" width="520" />
 
 ## Step 4: Creating a virtual machine to run Ubuntu 18.04
 
 Ubuntu 18.04 is the official version of Linux that is supported by both EOS, the EOS Plugin, and the versions of unity the plugin supports. It might not be limited to this version, but it is certainly the most widely used, so it is best to perform testing on at least this platform.
 
 1. Open Hyper-V Manager and select "Quick Create..." from the actions bar on the right-hand side.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/quick-create.png" width="537" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/quick-create.png" width="537" />
 
 2. Select "Ubuntu 18.04 LTS" and make sure that the Network switch selected is set to the virtual switch you created earlier.
 
-    <img src="/docs/images/hyperv_linux_guest_vm/ubuntu-18.04%20LTS.png" width="600" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/ubuntu-18.04-LTS.png" width="600" />
 
 3. Click "Create Virtual Machine" and wait for the process to complete.
    
 4.  Click `Edit Settings`
 
-    <img src="/docs/images/hyperv_linux_guest_vm/edit-settings.png" width="450" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/edit-settings.png" width="450" />
 
 5. Select the hard drive in the left panel, and click `Edit`
 
-    <img src="/docs/images/hyperv_linux_guest_vm/vm-settings.png" width="450" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/vm-settings.png" width="450" />
     
 6. Expand the drive to _at least_ 40GB
 
-    <img src="/docs/images/hyperv_linux_guest_vm/expand.png" width="450" />
+    <img src="/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/expand.png" width="450" />
 
 7. Once the Virtual Machine is created, connect to the virtual machine to complete the installation of Ubuntu.
     * When you get to the user creation portion of installation, make sure you do NOT enable "Log in automatically," as this will disable some of the capabilities that make using Hyper-V nice.
diff --git a/com.playeveryware.eos/Documentation~/dev_env/Ubuntu_Development_Environment.md b/com.playeveryware.eos/Documentation~/dev_env/Ubuntu_Development_Environment.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 # <div align="center">Configuring Ubuntu 18.04 for development</div>
 ---
diff --git a/com.playeveryware.eos/Documentation~/docs_on_docs/doc_style_guide.md b/com.playeveryware.eos/Documentation~/docs_on_docs/doc_style_guide.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 # <div align="center">Documentation Style Guide</div>
 ---
@@ -40,13 +40,13 @@ Each document should start (before the document title) with the PlayEveryWare, I
 Markdown:
 ```markdown
 <a href="/README.md">
-    <img src="/docs/images/PlayEveryWareLogo.gif" alt="PlayEveryWare, Inc. Logo" width="10%"/>
+    <img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="PlayEveryWare, Inc. Logo" width="10%"/>
 </a>
 ```
 
 What it looks like:
 
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="PlayEveryWare, Inc. Logo" width="10%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="PlayEveryWare, Inc. Logo" width="10%"/></a>
 
 ## Title:
 
@@ -138,7 +138,7 @@ What it looks like:
 
 ![unity tools package manager](/com.playeveryware.eos/Documentation~/images/unity_tools_package_manager.gif)
 
-Always place images in the `/docs/images/` directory of the repository. In most cases, it is also appropriate to add a subdirectory to the images directory in order to keep related images organized. For instance, when creating a new document that contains a variety of images, it would be wise to create a subdirectory in the images folder to contain all the images for that new document.
+Always place images in the `/com.playeveryware.eos/Documentation~/images/` directory of the repository. In most cases, it is also appropriate to add a subdirectory to the images directory in order to keep related images organized. For instance, when creating a new document that contains a variety of images, it would be wise to create a subdirectory in the images folder to contain all the images for that new document.
 
 > [!IMPORTANT] 
 > Never use an image in place of text (for instance do not take a screenshot of documentation from one area to include it in another). Aside from the issue of maintainability, the problem with this is that GitHub allows for dark and light modes, and the image will look wrong in one mode or the other. 
diff --git a/com.playeveryware.eos/Documentation~/frequently_asked_questions.md b/com.playeveryware.eos/Documentation~/frequently_asked_questions.md
@@ -152,4 +152,4 @@ Or to install the libraries manually, go to the `lib/NativeCode` folder, find th
 
 On the EOS Configuration Editor Window there is a setting for `Platform Flags`. By adding `DisableOverlay` to your list of Platform Flags, the Epic Overlay will not be initialized during runtime. When this is configured the `EOSBootstrapper.exe` will not be included in Windows builds.
 
-See [`PlatformFlags.cs`](/Assets/Plugins/Source/EOS_SDK/Generated/Platform/PlatformFlags.cs)
+See [`PlatformFlags.cs`](/com.playeveryware.eos/Runtime/EOS_SDK/Generated/Platform/PlatformFlags.cs)
diff --git a/com.playeveryware.eos/Documentation~/iOS/README_iOS.md b/com.playeveryware.eos/Documentation~/iOS/README_iOS.md
@@ -1,6 +1,6 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>
 
-<div align="center"> <img src="/docs/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
+<div align="center"> <img src="/com.playeveryware.eos/Documentation~/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
 
 
 # <div align="center">iOS Getting Started</div>
diff --git a/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/ubuntu-18.04-LTS.png b/com.playeveryware.eos/Documentation~/images/hyperv_linux_guest_vm/ubuntu-18.04-LTS.png
diff --git a/com.playeveryware.eos/Documentation~/macOS/README_macOS.md b/com.playeveryware.eos/Documentation~/macOS/README_macOS.md
@@ -1,6 +1,6 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
-<div align="center"> <img src="/docs/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
+<div align="center"> <img src="/com.playeveryware.eos/Documentation~/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>
 
 # <div align="center">macOS</div>
 ---
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/P2P_netcode_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/P2P_netcode_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **P2P Netcode Demo**
 This demo showcases the Peer 2 Peer interface working with Unity's netcode. This is done through a simple game where players can move a square around the screen.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/P2P_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/P2P_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Peer 2 Peer Demo**
 The Peer 2 Peer demo showcases the peer 2 peer interface. This is done through a basic messaging application where users can chat with other users on their friend list.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/achievements_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/achievements_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Achievements Demo**
 This demo showcases the Achievements function. This is done through 2 test achievements, one tracking logins and the other logging an arbitrary stat. Each Achievement has a unlocked and locked display name and description, as well as the ability to hide it and the relevant tracked data for it.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/auth&friends_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/auth&friends_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Auth & Friends Demo**
 This demo showcases an implementation of the friends list into a game UI. The panel on the right shows the user's friend list and status of each friend. This panel can be accessed in other scenes that require access to the friends list.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/customInvites_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/customInvites_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Custom Invites Demo**
 This demo showcases the custom invite functionality allowing for messaging with arbitrary payloads. This is meant for cases where an already existing invitation system exists. This demo allows users to send invites with a text payload to anyone on their friends list.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/leaderboards_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/leaderboards_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Leaderboards Demo**
 This demo showcases the leaderboard functionality to track scores across the player base with multiple filter methods such as global scores or only friend scores.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/lobbies_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/lobbies_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Lobbies Demo**
 This demo showcases the lobby and includes a voice chat interface in a combined demo. The demo functions as a waiting room style lobby where users can create a new lobby or join existing ones, once in a lobby users can communicate through the lobby voice chat.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/metrics_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/metrics_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Metrics Demo**
 The Metrics demo showcases the player metrics interface, allowing for game use and analytical data to be collected. This data can then be accessed through the developer portal for the product.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/performance_stress_test_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/performance_stress_test_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Performance Stress Test**
 This scene was created to test the performance of the overlay under different system conditions, it does not use any EOS systems outside of the overlay. It has the ability to change cpu usage, gpu usage, and memory usage.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/player_data_storage_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/player_data_storage_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Player Data Storage Demo**
 This demo showcases the Player Data Storage interface. This allows games to store player specific data in cloud servers. The demo uses a faux inventory to showcase this.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/player_reports_and_sanctions_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/player_reports_and_sanctions_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Player Reports and Sanctions Demo**
 This demo showcases the reports interface and sanctions interface. This is done through a report menu, and a display of any current sanctions on the user's account.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/sessions_and_matchmaking_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/sessions_and_matchmaking_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Sessions and Matchmaking**
 This demo showcases the sessions interface, users can create, manage and join sessions.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/store_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/store_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Store Demo**
 This demo showcases the store interface through a faux store.
diff --git a/com.playeveryware.eos/Documentation~/scene_walkthrough/title_storage_walkthrough.md b/com.playeveryware.eos/Documentation~/scene_walkthrough/title_storage_walkthrough.md
@@ -1,4 +1,4 @@
-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="README.md" width="5%"/></a>
 
 ## **Title Storage Demo**
 This demo showcases the title storage interface. This functions similar to the player data storage interface, although the data accessed is game/platform specific instead of player specific. This demo allows users to search files by tag and name and then view their contents. The demo is broken up into three parts, Tags search, File Search and the File viewer:
diff --git a/com.playeveryware.eos/Documentation~/standards.md b/com.playeveryware.eos/Documentation~/standards.md
@@ -119,4 +119,4 @@ Major.Minor.Patch
 
 ## Unit Testing
 
-See [our documentation on unit testing](/com.playeveryware.eos/Documentation~/unit-testing.md).
+See [our documentation on unit testing](/com.playeveryware.eos/Documentation~/unit_testing.md).
diff --git a/com.playeveryware.eos/README.md b/com.playeveryware.eos/README.md

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<a href="/readme.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>`
	`1`	`+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>`
`2`	`2`
`3`	`3`	`<div align="center"> <img src="/com.playeveryware.eos/Documentation~/images/EOSPluginLogo.png" alt="PlayEveryWare EOS Plugin for Unity" /> </div>`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<a href="/README.md"><img src="/docs/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>`
	`1`	`+<a href="/README.md"><img src="/com.playeveryware.eos/Documentation~/images/PlayEveryWareLogo.gif" alt="Lobby Screenshot" width="5%"/></a>`
`2`	`2`
`3`	`3`	`# <div align="center">Linking EOS Library on Android Settings</div>`
`4`	`4`	`---`
Original file line number	Diff line number	Diff line change
@@ -152,4 +152,4 @@ Or to install the libraries manually, go to the `lib/NativeCode` folder, find th
`152`	`152`
`153`	`153`	On the EOS Configuration Editor Window there is a setting for `Platform Flags`. By adding `DisableOverlay` to your list of Platform Flags, the Epic Overlay will not be initialized during runtime. When this is configured the `EOSBootstrapper.exe` will not be included in Windows builds.
`154`	`154`
`155`		-See [`PlatformFlags.cs`](/Assets/Plugins/Source/EOS_SDK/Generated/Platform/PlatformFlags.cs)
	`155`	+See [`PlatformFlags.cs`](/com.playeveryware.eos/Runtime/EOS_SDK/Generated/Platform/PlatformFlags.cs)