Graphics.RenderMeshIndirect arguments naming is misleading

Steps to reproduce:

1. Read https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Graphics.RenderMeshIndirect.html
2. Notice that 3rd argument is called "commandBuffer", and same wording is used in the whole explanation.

Actual results: 

Devs get confused with the Unity CommandBuffer type.

3rd argument is not a CommandBuffer but just a regular GraphicsBuffer.

 

Expected results: 

3rd arguments is renamed something less confusing such as "indirectDrawArgsBuffer"

Reproducible with versions: 

Not reproducible with versions: 

Can’t test with versions: 

Tested on (OS): 

Notes:

• The same problem exists in our internal source code.