Add tips in docs

[DeathVenom54]

Proposed change(s)

I updated a code block and added little tips to explain things better, ones I wish were included when I was first learning from the docs.

Types of change(s)

• Bug fix
• New feature
• Code refactor
• Breaking change
• Documentation update
• Other (please describe)

Checklist

• Added tests that prove my fix is effective or that my feature works
• Updated the changelog (if applicable)
• Updated the documentation (if applicable)
• Updated the migration guide (if applicable)

Other comments

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[miguelalonsojr]

@maryamhonari or @jrupert-unity can you have a look at this PR? Seems reasonable since it's a doc update.

[jrupert-unity]

Changes make some good improvements, but need work.

I would remove the change around line 234.
I'd remove line 270 and change 272&273 to use actionBuffers.ContinuousActions[]. Same with 319&320.
Line 264 should say ContinuousActions[] or actionBuffers.ContinuousActions[].
Line 443 should be "Make sure the behavior name in the 'Behavior Parameters' component matches the one in the config file." to fix spelling and punctuation.

[DeathVenom54]

Hey I am very new to OS contributions. I cannot see any options to edit the code in my pull request.

[jrupert-unity]

I think if you push more changes to the file the pull request will update. Alternatively if Miguel approves we can accept this pull request and I can update with my changes after that.

Add more commits by pushing to the main branch on DeathVenom54/ml-agents.

[DeathVenom54]

Alright, I'll do that

Edit: done