The conversion tools used during DocBook/LaTeX/Markdown->ReST conversion and some automatic rules which exists on certain text editors like LibreOffice turned ASCII characters into some UTF-8 alternatives that are better displayed on html and PDF. While it is OK to use UTF-8 characters in Linux, it is better to use the ASCII subset instead of using an UTF-8 equivalent character as it makes life easier for tools like grep, and are easier to edit with the some commonly used text/source code editors. Also, Sphinx already do such conversion automatically outside literal blocks: https://docutils.sourceforge.io/docs/user/smartquotes.html So, replace the occurences of the following UTF-8 characters: - U+2019 ('’'): RIGHT SINGLE QUOTATION MARK Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> --- Documentation/infiniband/tag_matching.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/infiniband/tag_matching.rst b/Documentation/infiniband/tag_matching.rst index ef56ea585f92..f7583b48963f 100644 --- a/Documentation/infiniband/tag_matching.rst +++ b/Documentation/infiniband/tag_matching.rst @@ -14,9 +14,9 @@ match the following source and destination parameters: The ordering rules require that when more than one pair of send and receive message envelopes may match, the pair that includes the earliest posted-send and the earliest posted-receive is the pair that must be used to satisfy the -matching operation. However, this doesn’t imply that tags are consumed in +matching operation. However, this doesn't imply that tags are consumed in the order they are created, e.g., a later generated tag may be consumed, if -earlier tags can’t be used to satisfy the matching rules. +earlier tags can't be used to satisfy the matching rules. When a message is sent from the sender to the receiver, the communication library may attempt to process the operation either after or before the -- 2.30.2
