Getting started in Unity doc updates

[analogrelay]

I don't have a Linear ticket for this because I'm basically just making small edits as I run through the tutorial to set up RG in my Unity game. I can create a ticket if we think it makes sense, but I figured I'd just open a draft and add my changes until I finish and then undraft it.

---

Find the pull request instructions here

Every reviewer and the owner of the PR should consider these points in their request (feel free to copy this checklist so you can fill it out yourself in the overall PR comment)

• [ ] The code is extensible and backward compatible
• [ ] New public interfaces are extensible and open to backward compatibility in the future
• [ ] If preparing to remove a field in the future (i.e. this PR removes an argument), the argument stays but is no longer functional, and attaches a deprecation warning. A linear task is also created to track this deletion task.
• [ ] Non-critical or potentially modifiable arguments are optional
• [ ] Breaking changes and the approach to handling them have been verified with the team (in the Linear task, design doc, or PR itself)
• [ ] The code is easy to read
• [ ] Unit tests are added for expected and edge cases
• [ ] Integration tests are added for expected and edge cases
• [ ] Functions and classes are documented
• [ ] Migrations for both up and down operations are completed
• [ ] A documentation PR is created and being reviewed for anything in this PR that requires knowledge to use
• [ ] Implications on other dependent code (i.e. sample games and sample bots) is considered, mentioned, and properly handled
• [ ] Style changes and other non-blocking changes are marked as non-blocking from reviewers

[vontell]

@analogrelay this is likely being resolved in my other PR, #50 - should we close this?

[analogrelay]

Ah yeah, this fell off my radar. I'm game to close and roll in to yours.