[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200729021120.35901-1-luc.vanoostenryck@gmail.com>
Date: Wed, 29 Jul 2020 04:11:20 +0200
From: Luc Van Oostenryck <luc.vanoostenryck@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Subject: [PATCH] doc: remove stray HTML entity in '<slash>'
An excerpt from POSIX contains three occurrences of '<slash>' but
the first two are spelled starting with an HTML entity: '<slash>'
Fix this by replacing the stray HTML entity by a '<'.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@...il.com>
---
Documentation/filesystems/path-lookup.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
index e2ba15146365..d46688d6770d 100644
--- a/Documentation/filesystems/path-lookup.rst
+++ b/Documentation/filesystems/path-lookup.rst
@@ -78,8 +78,8 @@ particular, ``mkdir()`` and ``rmdir()`` each create or remove a directory named
by the final component, and they are required to work with pathnames
ending in "``/``". According to POSIX_
- A pathname that contains at least one non- <slash> character and
- that ends with one or more trailing <slash> characters shall not
+ A pathname that contains at least one non-<slash> character and
+ that ends with one or more trailing <slash> characters shall not
be resolved successfully unless the last pathname component before
the trailing <slash> characters names an existing directory or a
directory entry that is to be created for a directory immediately
--
2.27.0
Powered by blists - more mailing lists