whats-new: minor fixes

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

diff --git a/contents/whats-new.md b/contents/whats-new.md
index 9c4df4673b3cae60814d4bee375b7ca8066ea1f9..471d04957b13f44c4d7cc7d24fe7bd4b6bc7b07c 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,16 +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, e.g.:
 
 <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
-[this release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/).
+[the release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/).