Minor documentation improvements

Author: jeffreylanters

documentation/docs/api/unload.md

@@ -15,7 +15,7 @@ The unload function is only available in Unity Builds created with Unity 2020.1
 :::
 
 :::warning
-Normally it was possible to unmount the Unity Application and unmount the containing component right after the unload function was invoked, but due to a bug in newer Unity version this is no longer possible when using a builds made with Unity 2021.2 or later. It is still possible to unload the Unity Application, but the canvas has to kept mounted until the promise is resolved. As of writing this, the issue has not been fixed, but it is possible to unmount the Unity Application manually by halting the navigation to the next page. A ticket has been openend, this is a know issue by the Unity team. More information can be found on the [issue on GitHub](https://github.com/jeffreylanters/react-unity-webgl/issues/250).
+Normally it was possible to unmount the Unity Application and unmount the containing component right after the unload function was invoked, but due to a bug in newer Unity versions this is no longer possible when using a build made with Unity 2021.2 or later. It is still possible to unload the Unity Application, but the canvas has to be kept mounted until the promise is resolved. As of writing this, the issue has not been fixed, but it is possible to unmount the Unity Application manually by halting the navigation to the next page. A ticket has been opened, this is a known issue by the Unity team. More information can be found on the [issue on GitHub](https://github.com/jeffreylanters/react-unity-webgl/issues/250).
 :::
 
 When building a multi-page React Application, it is important to unload the Unity Application in order to completely unmount the component from the DOM to free up the memory taken by the Unity JavaScript heap, and without Unity throwing an error. Invoking the function will request the Unity Application to be unloaded from memory. The function will return a Promise that will be resolved when the Unity Application has been unloaded.