Fixed up Doc Comments

[rikrak]

I noticed there were a few build warnings around the Doc Comments in the code, so I've updated and added so that there's now less noise in the build output.

Hopefully I've not mucked up the Git branching\fetching\merging with this one :-)

[kevinkuszyk]

Thanks @rikrak, I manually rebased and merged this one on my machine and it looks like GitHub didn't pickup the change as the commit hashes have changed. I'm going to close this PR, but don't worry your changes are in!

I think what's happened here, is that first commit to your master branch is resulting in merge commits when you are syncing up with the master here. Usually git would do a fast forward merge, but it can't in this case.

When you get a moment, it might be worth either creating a new master branch in your fork from the master here, or deleting your fork and starting over. Don't worry about losing your work for #34 as I have a copy of your commits in this repro in the rikrak/fa5-upgrade-rebased branch which you can pull into your fork if you need to make any changes.

I hope that makes sense, and thanks again for the contribution.

[rikrak]

Thanks. I shall delete and re-create the fork as that is much easier for me. :-)