Merging upstream version 2.7.1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/Documentation/nvme-wdc-vs-error-reason-identifier.html b/Documentation/nvme-wdc-vs-error-reason-identifier.html
index d107c8a..8f13214 100644
--- a/Documentation/nvme-wdc-vs-error-reason-identifier.html
+++ b/Documentation/nvme-wdc-vs-error-reason-identifier.html
@@ -758,7 +758,7 @@ nvme-wdc-vs-error-reason-identifier(1) Manual Page
 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>For the NVMe device given, retrieve the telemetry log error reason id field for either the host generated or

-controller initiated log.  The controller initiated telemetry log page option must be enabled to retrieve the

+controller initiated log. The controller initiated telemetry log page option must be enabled to retrieve the

 error reason id for that log page id.</p></div>

 <div class="paragraph"><p>The &lt;device&gt; parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).</p></div>

 <div class="paragraph"><p>This will only work on WDC devices supporting this feature.

@@ -836,7 +836,7 @@ Retrieves the controller initiated error reason identifier field and save it in
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2023-06-30 15:20:22 CEST

+ 2023-12-21 15:49:29 CET

 </div>

 </div>

 </body>