[PATCH] doc: Add blank line before bold text so it is rendered correctly

[PATCH] doc: Add blank line before bold text so it is rendered correctly

[eugene.loh]

From: Eugene Loh <eugene.loh@oracle.com>

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
 doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md | 1 +
 doc/userguide/reference/dtrace-ref-Variables.md               | 1 +
 doc/userguide/reference/dtrace_providers_io.md                | 1 +
 doc/userguide/reference/dtrace_providers_lockstat.md          | 1 +
 doc/userguide/reference/dtrace_providers_proc.md              | 1 +
 5 files changed, 5 insertions(+)

diff --git a/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md b/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
index e9239026f..641f666d9 100644
--- a/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
+++ b/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
@@ -132,6 +132,7 @@ Returns 1 \(true\)
 Returns 0 \(false\)
 
 </td></tr><tbody></table>
+
 **Note:**
 
 Identical Unicode strings might compare as being different if one or the other of the strings isn't normalized.
diff --git a/doc/userguide/reference/dtrace-ref-Variables.md b/doc/userguide/reference/dtrace-ref-Variables.md
index d3afa3833..70e214c14 100644
--- a/doc/userguide/reference/dtrace-ref-Variables.md
+++ b/doc/userguide/reference/dtrace-ref-Variables.md
@@ -167,6 +167,7 @@ Yes
 Any probe that fires accesses an instance of the variable specific to that particular firing of the probe.
 
 </td></tr><tbody></table>
+
 **Note:**
 
 Note the following information:
diff --git a/doc/userguide/reference/dtrace_providers_io.md b/doc/userguide/reference/dtrace_providers_io.md
index 40851042c..67c5c7d34 100644
--- a/doc/userguide/reference/dtrace_providers_io.md
+++ b/doc/userguide/reference/dtrace_providers_io.md
@@ -139,6 +139,7 @@ Probe
 `fileinfo_t *`
 
 </td></tr><tbody></table>
+
 **Note:**
 
 DTrace doesn't provide the option to use `fileinfo_t` with `io` probes. In Linux, no information is accessible at the level where the `io` probes fire about the file where an I/O request originated.
diff --git a/doc/userguide/reference/dtrace_providers_lockstat.md b/doc/userguide/reference/dtrace_providers_lockstat.md
index c1d3eb4de..d21c526d2 100644
--- a/doc/userguide/reference/dtrace_providers_lockstat.md
+++ b/doc/userguide/reference/dtrace_providers_lockstat.md
@@ -241,6 +241,7 @@ Probe
 —
 
 </td></tr><tbody></table>
+
 **Note:**
 
 `args[0]` has a pointer to the lock in question. The probes that fire in case of contention report a `uint64_t` `args[1]`, which is the wait time in nanoseconds. The `rw` probes also report an `int` that's either `RW_READER` or `RW_WRITER`. Finally, `adaptive-acquire-error` reports an `int` with a non zero error.
diff --git a/doc/userguide/reference/dtrace_providers_proc.md b/doc/userguide/reference/dtrace_providers_proc.md
index d799efd72..3ac8b706a 100644
--- a/doc/userguide/reference/dtrace_providers_proc.md
+++ b/doc/userguide/reference/dtrace_providers_proc.md
@@ -124,6 +124,7 @@ Fires when a signal is sent to a process or to a thread created by a process. Th
 Fires in the context of a newly created process. The `start` probe fires before any user-level instructions are executed in the process.
 
 </td></tr><tbody></table>
+
 **Note:**
 
 No fundamental difference between a process and a thread that a process creates, exists in Linux. The threads of a process are set up so that they can share resources, but each thread has its own entry in the process table with its own process ID.
-- 
2.47.3

Re: [DTrace-devel] [PATCH] doc: Add blank line before bold text so it is rendered correctly

[Elena Zannoni]

Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>


On 10/23/25 5:16 PM, eugene.loh--- via DTrace-devel wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
> 
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> ---
>  doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md | 1 +
>  doc/userguide/reference/dtrace-ref-Variables.md               | 1 +
>  doc/userguide/reference/dtrace_providers_io.md                | 1 +
>  doc/userguide/reference/dtrace_providers_lockstat.md          | 1 +
>  doc/userguide/reference/dtrace_providers_proc.md              | 1 +
>  5 files changed, 5 insertions(+)
> 
> diff --git a/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md b/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
> index e9239026f..641f666d9 100644
> --- a/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
> +++ b/doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md
> @@ -132,6 +132,7 @@ Returns 1 \(true\)
>  Returns 0 \(false\)
>  
>  </td></tr><tbody></table>
> +
>  **Note:**
>  
>  Identical Unicode strings might compare as being different if one or the other of the strings isn't normalized.
> diff --git a/doc/userguide/reference/dtrace-ref-Variables.md b/doc/userguide/reference/dtrace-ref-Variables.md
> index d3afa3833..70e214c14 100644
> --- a/doc/userguide/reference/dtrace-ref-Variables.md
> +++ b/doc/userguide/reference/dtrace-ref-Variables.md
> @@ -167,6 +167,7 @@ Yes
>  Any probe that fires accesses an instance of the variable specific to that particular firing of the probe.
>  
>  </td></tr><tbody></table>
> +
>  **Note:**
>  
>  Note the following information:
> diff --git a/doc/userguide/reference/dtrace_providers_io.md b/doc/userguide/reference/dtrace_providers_io.md
> index 40851042c..67c5c7d34 100644
> --- a/doc/userguide/reference/dtrace_providers_io.md
> +++ b/doc/userguide/reference/dtrace_providers_io.md
> @@ -139,6 +139,7 @@ Probe
>  `fileinfo_t *`
>  
>  </td></tr><tbody></table>
> +
>  **Note:**
>  
>  DTrace doesn't provide the option to use `fileinfo_t` with `io` probes. In Linux, no information is accessible at the level where the `io` probes fire about the file where an I/O request originated.
> diff --git a/doc/userguide/reference/dtrace_providers_lockstat.md b/doc/userguide/reference/dtrace_providers_lockstat.md
> index c1d3eb4de..d21c526d2 100644
> --- a/doc/userguide/reference/dtrace_providers_lockstat.md
> +++ b/doc/userguide/reference/dtrace_providers_lockstat.md
> @@ -241,6 +241,7 @@ Probe
>  —
>  
>  </td></tr><tbody></table>
> +
>  **Note:**
>  
>  `args[0]` has a pointer to the lock in question. The probes that fire in case of contention report a `uint64_t` `args[1]`, which is the wait time in nanoseconds. The `rw` probes also report an `int` that's either `RW_READER` or `RW_WRITER`. Finally, `adaptive-acquire-error` reports an `int` with a non zero error.
> diff --git a/doc/userguide/reference/dtrace_providers_proc.md b/doc/userguide/reference/dtrace_providers_proc.md
> index d799efd72..3ac8b706a 100644
> --- a/doc/userguide/reference/dtrace_providers_proc.md
> +++ b/doc/userguide/reference/dtrace_providers_proc.md
> @@ -124,6 +124,7 @@ Fires when a signal is sent to a process or to a thread created by a process. Th
>  Fires in the context of a newly created process. The `start` probe fires before any user-level instructions are executed in the process.
>  
>  </td></tr><tbody></table>
> +
>  **Note:**
>  
>  No fundamental difference between a process and a thread that a process creates, exists in Linux. The threads of a process are set up so that they can share resources, but each thread has its own entry in the process table with its own process ID.