Remove latin abbreviations

[lttng-docs.git] / contents / nuts-and-bolts / intro.md

diff --git a/contents/nuts-and-bolts/intro.md b/contents/nuts-and-bolts/intro.md
index 15d5808fa2ec113e2e5c0d3962c5dbfcb3f0080f..ba77f895b3d78c37f5a8f29b79b64f186a37405b 100644 (file)
--- a/contents/nuts-and-bolts/intro.md
+++ b/contents/nuts-and-bolts/intro.md
@@ -19,11 +19,11 @@ One major achievement in this field is, inarguably, the
 <a href="https://www.gnu.org/software/gdb/" class="ext">GNU debugger
 (GDB)</a>, which is an essential tool for developers to find and fix
 bugs. But even the best debugger won't help make your software run
-faster, and nowadays, faster softwares means either more work done by
+faster, and nowadays, faster software means either more work done by
 the same hardware, or cheaper hardware for the same work.
 
 A _profiler_ is often the tool of choice to identify performance
-bottleneck. Profiling is suitable to identify _where_ performance is
+bottlenecks. Profiling is suitable to identify _where_ performance is
 lost in a given software; the profiler outputs a profile, a
 statistical summary of observed events, which you may use to know
 which functions took the most time to execute. However, a profiler
@@ -43,12 +43,12 @@ possibility of resolving a wide range of problems that are otherwise
 extremely challenging.
 
 Tracing is often compared to _logging_. However, tracers and loggers
-are two different tools, serving two different purposes. Tracers are
+are two different types of tools, serving two different purposes. Tracers are
 designed to record much lower-level events that occur much more
 frequently than log messages, often in the thousands per second range,
 with very little execution overhead. Logging is more appropriate for
 very high-level analysis of less frequent events: user accesses,
-exceptional conditions (e.g., errors, warnings), database
+exceptional conditions (errors and warnings, for example), database
 transactions, instant messaging communications, etc. More formally,
 logging is one of several use cases that can be accomplished with
 tracing.
@@ -63,7 +63,7 @@ achieve this.
 So, in the end, this is what LTTng is: a powerful, open source set of
 tools to trace the Linux kernel and user applications. LTTng is
 composed of several components actively maintained and developed by
-its community.
+its <a href="/community/#where" class="ext">community</a>.
 
 Excluding proprietary solutions, a few competing software tracers
 exist for Linux.
@@ -85,7 +85,7 @@ overhead amongst other solutions.  It produces trace files in the
 format, an optimized file format for production and analyses of
 multi-gigabyte data. LTTng is the result of close to 10 years of
 active development by a community of passionate developers. It is
-currently available on all major desktop and embedded Linux
+currently available on all major desktop, server, and embedded Linux
 distributions.
 
 The main interface for tracing control is a single command line tool