From cad912e9b576abe5f734a3bb7b919ef2e6a29029 Mon Sep 17 00:00:00 2001 From: Christophe Bedard Date: Wed, 3 Nov 2021 09:41:36 -0400 Subject: [PATCH] 2.5-2.13: fix use of 'weighs' Signed-off-by: Christophe Bedard --- 2.10/lttng-docs-2.10.txt | 2 +- 2.11/lttng-docs-2.11.txt | 2 +- 2.12/lttng-docs-2.12.txt | 2 +- 2.13/lttng-docs-2.13.txt | 2 +- 2.5/lttng-docs-2.5.txt | 2 +- 2.6/lttng-docs-2.6.txt | 2 +- 2.7/lttng-docs-2.7.txt | 2 +- 2.8/lttng-docs-2.8.txt | 2 +- 2.9/lttng-docs-2.9.txt | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/2.10/lttng-docs-2.10.txt b/2.10/lttng-docs-2.10.txt index 375fcf5..a98b6a8 100644 --- a/2.10/lttng-docs-2.10.txt +++ b/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 diff --git a/2.11/lttng-docs-2.11.txt b/2.11/lttng-docs-2.11.txt index 9d5d083..64ea9e5 100644 --- a/2.11/lttng-docs-2.11.txt +++ b/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 diff --git a/2.12/lttng-docs-2.12.txt b/2.12/lttng-docs-2.12.txt index 4b87947..8eaf0f7 100644 --- a/2.12/lttng-docs-2.12.txt +++ b/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 diff --git a/2.13/lttng-docs-2.13.txt b/2.13/lttng-docs-2.13.txt index 2ba2d76..6d0e906 100644 --- a/2.13/lttng-docs-2.13.txt +++ b/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 diff --git a/2.5/lttng-docs-2.5.txt b/2.5/lttng-docs-2.5.txt index 3a2c9ce..ea80a7a 100644 --- a/2.5/lttng-docs-2.5.txt +++ b/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 diff --git a/2.6/lttng-docs-2.6.txt b/2.6/lttng-docs-2.6.txt index 7626c89..b04fc05 100644 --- a/2.6/lttng-docs-2.6.txt +++ b/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 diff --git a/2.7/lttng-docs-2.7.txt b/2.7/lttng-docs-2.7.txt index 6d78323..145edc3 100644 --- a/2.7/lttng-docs-2.7.txt +++ b/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 diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt index 9ccf4ca..c659f82 100644 --- a/2.8/lttng-docs-2.8.txt +++ b/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 diff --git a/2.9/lttng-docs-2.9.txt b/2.9/lttng-docs-2.9.txt index 53d575f..1ea6aa3 100644 --- a/2.9/lttng-docs-2.9.txt +++ b/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