Some Mistakes in the Unity Documentation

Hi,

[Solved]
Here on the right side you will see:

17. Events
18. Attributes

But here you will see:

17. Attributes
18. Events

[Solved]
Here you should to replace "Humandoid Class" to "Humanoid Class".

 

[Not solved]
You should to add '\n' here in the end (before of last '}') of the code section Player:

Code (CSharp):

1.     //This is an example of an auto-implemented
2.     //property
3.     public int Health{ get; set;}}

 

(These are problems on the learn/tutorial sections, not the docs.)

 

[Solved]
Here on the right side: "Editor Scripting Scripting"

 

[Solved]
After updating all the Facebook Likes have been removed.

 

[Not solved]
Here instead of (menu: GameObject > Create General > Particle System)
You should to write (menu: GameObject > Particle System)

[Not solved]
Here instead of (menu: Assets > Import Package > Particles)
You should to write (menu: Assets > Import Package > ParticleSystems)

 

@8Observer8 Thanks for finding these details. You might take the trophy from me, which was awarded for finding the most number of issues in documentation!

The best way to report documentation issues is throught the in-editor bug reporter. This will go into a triage queue and be handled directly by documentation with their internal tools. As documentations (especially the scripting reference) is tied into specific releases of the softwware, they have specialsed tools and piplelines to handle these issues.

Use the in house bug reporter:


Choose documentation and always:



Then include the page URL (like you did in the post) and a clear description of the issue (which you've done in the post) and they'll get it in as soon as possible.

Due to the way that documentation is rolled out, it may be fixed internally before you see it fixed on the site.

Thanks for the sharp eyes!

[Ratz! Crossposted! Sorry James!]

 

Oh, by the way - this is somewhat the issue that Graham was mentioning above. James and I can help fix items on the learn site in our content management system, but true documentation issues need to be handled by documentation.

 

Hi, guys! Ok, I will use the "Bug Reporter". It looks more comfortable. Thanks!