[PATCH 0/3] Documentation: trace: eliminate doubled words

[PATCH 0/3] Documentation: trace: eliminate doubled words

[Randy Dunlap]

Fix doubled (duplicated) words in trace documentation.

Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>


 Documentation/trace/ftrace.rst           |    4 ++--
 Documentation/trace/histogram-design.rst |    4 ++--
 Documentation/trace/stm.rst              |    4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

[PATCH 1/3] Documentation: trace/ftrace: drop doubled words

[Randy Dunlap]

Drop the doubled words "for" and "that".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
---
 Documentation/trace/ftrace.rst |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20200701.orig/Documentation/trace/ftrace.rst
+++ linux-next-20200701/Documentation/trace/ftrace.rst
@@ -561,7 +561,7 @@ of ftrace. Here is a list of some of the
 
   trace_marker_raw:
 
-	This is similar to trace_marker above, but is meant for for binary data
+	This is similar to trace_marker above, but is meant for binary data
 	to be written to it, where a tool can be used to parse the data
 	from trace_pipe_raw.
 
@@ -1394,7 +1394,7 @@ an example::
    => x86_64_start_reservations
    => x86_64_start_kernel
 
-Here we see that that we had a latency of 16 microseconds (which is
+Here we see that we had a latency of 16 microseconds (which is
 very good). The _raw_spin_lock_irq in run_timer_softirq disabled
 interrupts. The difference between the 16 and the displayed
 timestamp 25us occurred because the clock was incremented

[PATCH 2/3] Documentation: trace/histogram-design: drop doubled words

[Randy Dunlap]

Drop the doubled words "to" and "the".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
---
 Documentation/trace/histogram-design.rst |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20200701.orig/Documentation/trace/histogram-design.rst
+++ linux-next-20200701/Documentation/trace/histogram-design.rst
@@ -780,7 +780,7 @@ same part of the hist_data->fields[] arr
 Moving on to the sched_switch trigger hist_debug output, in addition
 to the unused wakeup_lat variable, we see a new section displaying
 variable references.  Variable references are displayed in a separate
-section because in addition to to being logically separate from
+section because in addition to being logically separate from
 variables and values, they actually live in a separate hist_data
 array, var_refs[].
 
@@ -863,7 +863,7 @@ event.
 The onmatch() action below basically says that whenever we have a
 sched_switch event, if we have a matching sched_waking event, in this
 case if we have a pid in the sched_waking histogram that matches the
-the next_pid field on this sched_switch event, we retrieve the
+next_pid field on this sched_switch event, we retrieve the
 variables specified in the wakeup_latency() trace action, and use
 them to generate a new wakeup_latency event into the trace stream.
 

[PATCH 3/3] Documentation: trace/stm: drop doubled words

[Randy Dunlap]

Change "and and" to "and an".
Fix spello of "example".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
 Documentation/trace/stm.rst |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20200701.orig/Documentation/trace/stm.rst
+++ linux-next-20200701/Documentation/trace/stm.rst
@@ -33,8 +33,8 @@ This policy is a tree structure containi
 have a name (string identifier) and a range of masters and channels
 associated with it, located in "stp-policy" subsystem directory in
 configfs. The topmost directory's name (the policy) is formatted as
-the STM device name to which this policy applies and and arbitrary
-string identifier separated by a stop. From the examle above, a rule
+the STM device name to which this policy applies and an arbitrary
+string identifier separated by a stop. From the example above, a rule
 may look like this::
 
 	$ ls /config/stp-policy/dummy_stm.my-policy/user

Re: [PATCH 0/3] Documentation: trace: eliminate doubled words

[Jonathan Corbet]

On Fri,  3 Jul 2020 14:24:50 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> Fix doubled (duplicated) words in trace documentation.
> 
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> 
> 
>  Documentation/trace/ftrace.rst           |    4 ++--
>  Documentation/trace/histogram-design.rst |    4 ++--
>  Documentation/trace/stm.rst              |    4 ++--
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 
Applied, thanks.

jon