Updated the FAQ and changed some of the formatting.

[jacobsky]

@Bromeon As I mentioned via discord, I went through the issues and extrapolated on cleaned up the FAQ a bit.
Also added a fix to have the logging recipe get added to the summary as it was previously missing.

[Bromeon]

Thank you very much, your changes add some extremely valuable insights 👍🏼

I tried to be quite open about my thoughts, so expect lots of comments 🙂

In cases where I added code or text, it can make sense if you use the "Quote comment" function to get the original formatting -- this is especially true for links within this repo, which are sugared by GitHub. Also feel free to copy-paste anything verbatim.

Some general consistency remarks: maybe check the capitalization of a few keywords -- Rust, Godot, godot-rust, GDNative, GDScript. At some point in the distant future I might add CI checks for those 😛

[jacobsky]

@Bromeon Thank you for all the valuable insight. I've gone ahead and incorporated your changes. I appreciate the thorough look into the full FAQ. If you have any additional changes, please feel free to let me know.

[jacobsky]

@Bromeon Alrighty. I think the most recent push should resolve the last of the changes. Please let me know if there's anything else that needs doing :)

[jacobsky]

Also I just noticed, but I believe this resolves issue #23 and possibly #5

[Bromeon]

It also overlaps somewhat with godot-rust/book#24.
That would be 4-in-1, do you think we'll manage 5? 😬

[jacobsky]

@Bromeon To ensure that we can close #5 I went ahead and added a section on profiling to "code-faq.md" at the bottom. I'm starting to think that I'll need to work on another PR to make some sub-sections for "code-faq" since it's getting pretty long and a little mixed up/hard to follow.

[Bromeon]

I agree, this PR is already big enough, we can always add more and refine things in the future 🙂

[Bromeon]

Thanks a lot for this huge contribution! Will definitely help a lot of newcomers to navigate 🙂