From ac5d575e9c9da945333177286c5f6a70a8cc874b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kamil=20=C5=9Aliwak?= Date: Tue, 27 Sep 2022 15:33:22 +0200 Subject: [PATCH] path-resolution.rst: Typo, segument -> segment --- docs/path-resolution.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/path-resolution.rst b/docs/path-resolution.rst index 40a727068..2c2fab766 100644 --- a/docs/path-resolution.rst +++ b/docs/path-resolution.rst @@ -197,7 +197,7 @@ source unit name. A source unit name is just an identifier and even if its value happens to look like a path, it is not subject to the normalization rules you would typically expect in a shell. - Any ``/./`` or ``/../`` seguments or sequences of multiple slashes remain a part of it. + Any ``/./`` or ``/../`` segments or sequences of multiple slashes remain a part of it. When the source is provided via Standard JSON interface it is entirely possible to associate different content with source unit names that would refer to the same file on disk.