Remove unneeded "will"s + minor fixes

[lttng-docs.git] / contents / using-lttng / instrumenting / c-application / defining-tracepoints.md

diff --git a/contents/using-lttng/instrumenting/c-application/defining-tracepoints.md b/contents/using-lttng/instrumenting/c-application/defining-tracepoints.md
index e9e007d18f6a2905d5ae3faea91859250e2b1ae5..bd6c07648e90c79b7676ae0c26041b7746ffe832 100644 (file)
--- a/contents/using-lttng/instrumenting/c-application/defining-tracepoints.md
+++ b/contents/using-lttng/instrumenting/c-application/defining-tracepoints.md
@@ -37,7 +37,7 @@ provider in which this tracepoint is defined
 (see [Tracepoint provider](#doc-tracepoint-provider)). In other words,
 always use the same string as the value of `TRACEPOINT_PROVIDER` above.
 
-The tracepoint name will become the event name once events are recorded
+The tracepoint name becomes the event name once events are recorded
 by the LTTng-UST tracer. It must follow the tracepoint provider name
 syntax: start with a letter and contain either letters, numbers or
 underscores. Two tracepoints under the same provider cannot have the
@@ -47,8 +47,8 @@ overload functions and methods in C++/Java.
 <div class="tip">
 <p><span class="t">Note:</span>The concatenation of the tracepoint
 provider name and the tracepoint name cannot exceed 254 characters. If
-it does, the instrumented application will compile and run, but LTTng
-will issue multiple warnings and you could experience serious problems.</p>
+it does, the instrumented application compiles and runs, but LTTng
+issues multiple warnings and you could experience serious problems.</p>
 </div>
 
 The list of tracepoint arguments gives this tracepoint its signature:
@@ -65,16 +65,16 @@ library's `fseek()`, the `TP_ARGS()` part would look like:
     ),
 ~~~
 
-Of course, you will need to include appropriate header files before
+Of course, you need to include appropriate header files before
 the `TRACEPOINT_EVENT()` macro calls if any argument has a complex type.
 
 `TP_ARGS()` may not be omitted, but may be empty. `TP_ARGS(void)` is
 also accepted.
 
 The list of fields is where the fun really begins. The fields defined
-in this list will be the fields of the events generated by the execution
+in this list are the fields of the events generated by the execution
 of this tracepoint. Each tracepoint field definition has a C
-_argument expression_ which will be evaluated when the execution reaches
+_argument expression_ which is evaluated when the execution reaches
 the tracepoint. Tracepoint arguments _may be_ used freely in those
 argument expressions, but they _don't_ have to.