plumbing-overview: minor fixes

[lttng-docs.git] / contents / whats-new.md

diff --git a/contents/whats-new.md b/contents/whats-new.md
index 7d42d3c9b2e5fa45f09732a3b3bdab3ea1cfb553..d5a00066ce982f091fb6888ad454ca9bbe84e69e 100644 (file)
--- a/contents/whats-new.md
+++ b/contents/whats-new.md
@@ -4,7 +4,7 @@ id: whats-new
 
 Most of the changes of LTTng 2.6 are bug fixes, making the toolchain
 more stable than ever before. Still, LTTng 2.6 adds some interesting
-features.
+features to the project.
 
 LTTng 2.5 already supported the instrumentation and tracing of
 [Java applications](#doc-java-application) through `java.util.logging`
@@ -15,13 +15,16 @@ commands of the `lttng` tool.
 
 LTTng-modules has supported system call tracing for a long time,
 but until now, it was only possible to record either all of them,
-or none of them. LTTng 2.6 allows the user to record only a specific
-subset of system call events, e.g.:
+or none of them. LTTng 2.6 allows the user to record specific
+system call events, for example:
 
 <pre class="term">
 lttng enable-event --kernel --syscall open,fork,chdir,pipe
 </pre>
 
-Finally, the `lttng` command line tool cannot only communicate with
-humans as it used to do, but also with machines thanks to its new
+Finally, the `lttng` command line tool is not only able to communicate
+with humans as it used to do, but also with machines thanks to its new
 [machine interface](#doc-mi) feature.
+
+To learn more about the new features of LTTng 2.6, see
+[the release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/).