tracing: Fix doc mistakes in trace sample

 *         __entry->bar.x = y;

 *   __array: There are three fields (type, name, size). The type is the

 *         type of elements in teh array, the name is the name of the array.

 *         type of elements in the array, the name is the name of the array.

 *         size is the number of items in the array (not the total size).

 *

 *         __array( char, foo, 10) is the same as saying: char foo[10];

 *         type is the type of the element, name is the name of the array.

 *         The size is different than __array. It is not a static number,

 *         but the algorithm to figure out the length of the array for the

 *         specific instance of tracepoint. Again, size is the numebr of

 *         specific instance of tracepoint. Again, size is the number of

 *         items in the array, not the total length in bytes.

 *

 *         __dynamic_array( int, foo, bar) is similar to: int foo[bar];

 *         Notice, that "__entry" is not needed here.

 *

 *   __string: This is a special kind of __dynamic_array. It expects to

 *         have a nul terminated character array passed to it (it allows

 *         have a null terminated character array passed to it (it allows

 *         for NULL too, which would be converted into "(null)"). __string

 *         takes two paramenter (name, src), where name is the name of

 *         takes two parameter (name, src), where name is the name of

 *         the string saved, and src is the string to copy into the

 *         ring buffer.

 *

/*

 * Here's a better way for the previous samples (except, the first

 * exmaple had more fields and could not be used here).

 * example had more fields and could not be used here).

 */

DEFINE_EVENT(foo_template, foo_with_template_simple,

	TP_PROTO(const char *foo, int bar),