Fabri's feedback

Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>

Author: chalin

content/en/docs/concepts/instrumentation/_index.md

@@ -5,7 +5,7 @@ aliases: [instrumenting]
 weight: 15
 ---
 
-For a system [observable], it must be **instrumented**: that is, code from the
+For a system to be [observable], it must be **instrumented**: that is, code from the
 system's components must emit [signals], such as [traces], [metrics], and
 [logs].
 
@@ -36,7 +36,7 @@ solutions. The following things are also a part of OpenTelemetry:
 - Libraries can leverage the OpenTelemetry API as a dependency, which will have
   no impact on applications using that library, unless the OpenTelemetry SDK is
   imported.
-- For each of the [signals] you have several methods at your disposals to
+- For each of the [signals] you have several methods at your disposal to
   create, process, and export them.
 - With [context propagation](../context-propagation/) built into the
   implementations, you can correlate signals regardless of where they are

content/en/docs/what-is-opentelemetry.md

@@ -15,7 +15,7 @@ OpenTelemetry is:
 
   of [telemetry data][] such as [traces], [metrics], and [logs].
 
-- **Open source** and **vendor- and tool-agnostic**, meaning that it can be used
+- **Open source**, as well as **vendor- and tool-agnostic**, meaning that it can be used
   with a broad variety of observability backends, including open source tools
   like [Jaeger] and [Prometheus], as well as commercial offerings. OpenTelemetry
   is **not** an observability backend itself.
@@ -24,7 +24,7 @@ A major goal of OpenTelemetry is to enable easy instrumentation of your
 applications and systems, regardless of the programming language,
 infrastructure, and runtime environments used.
 
-The (backend) **storage** and (frontend) **visualization** of telemetry data are
+The backend (storage) and the frontend (visualization) of telemetry data are
 intentionally left to other tools.
 
 ## What is observability?