2.5-2.13: fix use of 'weighs'

2.10/lttng-docs-2.10.txt

@@ -1261,7 +1261,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big

2.11/lttng-docs-2.11.txt

@@ -1535,7 +1535,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big

2.12/lttng-docs-2.12.txt

@@ -1673,7 +1673,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big

2.13/lttng-docs-2.13.txt

@@ -1636,7 +1636,7 @@ frequency.
 
 Note that LTTng uses https://diamon.org/ctf/[CTF] as its trace format,
 which means event record data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Therefore, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Therefore, a
 sub-buffer size of 1{nbsp}MiB is considered large.
 
 The previous scenarios highlight the major trade-off between a few large

2.5/lttng-docs-2.5.txt

@@ -954,7 +954,7 @@ Low memory system::
 
 You should know that LTTng uses CTF as its trace format, which means
 event data is very compact. For example, the average LTTng Linux kernel
-event weights about 32{nbsp}bytes. A sub-buffer size of 1{nbsp}MiB is
+event weighs about 32{nbsp}bytes. A sub-buffer size of 1{nbsp}MiB is
 thus considered big.
 
 The previous situations highlight the major trade-off between a few big

2.6/lttng-docs-2.6.txt

@@ -1006,7 +1006,7 @@ Low memory system::
 
 You should know that LTTng uses CTF as its trace format, which means
 event data is very compact. For example, the average LTTng Linux kernel
-event weights about 32{nbsp}bytes. A sub-buffer size of 1{nbsp}MiB is
+event weighs about 32{nbsp}bytes. A sub-buffer size of 1{nbsp}MiB is
 thus considered big.
 
 The previous situations highlight the major trade-off between a few big

2.7/lttng-docs-2.7.txt

@@ -1212,7 +1212,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big

2.8/lttng-docs-2.8.txt

@@ -1304,7 +1304,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big

2.9/lttng-docs-2.9.txt

@@ -1263,7 +1263,7 @@ frequency.
 
 Note that LTTng uses http://diamon.org/ctf/[CTF] as its trace format,
 which means event data is very compact. For example, the average
-LTTng kernel event record weights about 32{nbsp}bytes. Thus, a
+LTTng kernel event record weighs about 32{nbsp}bytes. Thus, a
 sub-buffer size of 1{nbsp}MiB is considered big.
 
 The previous situations highlight the major trade-off between a few big