Some minor errors

Hi. I’m new to Unity and I need to say that I’m really impressed about what and how Unity can to do with easy.
I’m reading the docs and I’ve found some little mistakes that could be easy to fix so I guess it is a good idea to post about it here. So, there it goes:

In Unity Manual > User Guide > Building Scenes > GameObjects,
“The GameObject-Script Relationship”, there’s a duplicated “and” in this phrase:
“When you create a script and attach it to a GameObject,”.

In Unity Manual > User Guide > Building Scenes > Using Components, before last line:
“Then you would be able access”, isn’t it “Then you would be able to access” ?

In Unity Manual > User Guide > Building Scenes > Cameras, “Depth Only”, there’s a
duplicated “to” in this phrase:
“The weapon Camera’s Clear Flags should be set to depth only.”.

In Unity Manual > User Guide > Building Scenes > Cameras, “Clip Planes”, second line:
“are measured from the its position”, isn’t it “are measured from its position” ?

Unity Manual > User Guide > Building Scenes > Particle Systems, “Mesh Particle Emitter”
section has duplicated blocks of text relative to “Ellipsoid Particle Emitter”.

Reference Manual > Terrain Engine Guide > Grass, “Editing Grass”, first line:
“select it choose Edit Details button->Edit.”, isn’t it
“select it and choose Edit Details button->Edit.” ?

In Unity Manual > User Guide > Working with Assets > Importing Assets, “Textures”:
The manual says that power of two textures are 32x32, 64x64, etc. There should be
explained that “power of two” textures doesn’t mean the width must be the same as
height, it means that both width and height must be of sizes supported by the graphics
card. It can be 32x32, 32x64, 64x128, 256x1024, etc. X and Y are not the same, but its
“bits size” still both power of two.

In Unity Manual > User Guide > Working with Assets > Using Scripts, “Attaching scripts
to objects”:
“If you have changed the name of your script, you will that name instead.”, isn’t it
“If you have changed the name of your script, you will see that name instead.” ?

In Unity Manual > User Guide > Working with Assets > Behind the Scenes,
“Behind the Scenes”, first line:
There is an illegal character before the word “manages”.

In Unity Manual > User Guide > Working with Assets > Behind the Scenes,
“Behind the Scenes”, sixth line:
There’s a duplicated “as” in the phrase “As user, you should never have
to manually alter the Library folder.”.

In Unity Manual > User Guide > Creating Gameplay > Instantiating Prefabs at runtime,
“Instantiating rockets explosions”, in the code sample:
“// This way we the user can not assign a prefab without rigidbody”, isn’t it
“// This way the user can not assign a prefab without rigidbody” ?

In Unity Manual > User Guide > Creating Gameplay > Physics, “Collision action matrix”:
The chart is too much confusing. A chart with columns and rolls may be much better.

In Unity Manual > User Guide > Creating Gameplay > Physics:
The “Triggers” sections are duplicated blocks of text relative to the “Triggers” section
of the “Sphere Collider” manual. The “Friction and bounciness” section is duplicated too.

In Reference Manual > Animation View Guide > Using Animation Events, under the third
image:
“You can quickly get see what a specific Animation Event does…”, isn’t it
“You can quickly to see what a specific Animation Event does…” ?

In Reference Manual > GUI Scripting Guide > GUI Basics, after first code sample:
“If you copy/paste this script and attach it a GameObject,”, isn’t it
“If you copy/paste this script and attach it to a GameObject,” ?

In Reference Manual > GUI Scripting Guide > Controls, Button, “Basic Usage”:
There’s a duplicated “the” in the phrase “you wrap the GUI.Button function in an if
statement.”. The same error is in the same section of the RepeatButton manual.

Nothing really serious, but there’s no reason to let it stay like that right? :slight_smile:

Actually it’s unlikely to get looked at here by the right people; you should use the bug reporter instead, which has a category for documentation errors.

–Eric

You sure have an impressive collection, for this being your first post! I haven’t logged half that many documentation errors via the Bug Reporter.