fix ambiguous relative links example

Author: theMomax

Sources/SwiftDocC/SwiftDocC.docc/SwiftDocC/LinkResolution.md

@@ -28,18 +28,20 @@ Both types of links can be used in a relative or absolute way. Absolute symbol l
 
 To make authored documentation links easier to write and easier to read in plain text format all authored documentation links can be written as relative links. The symbol links in documentation extension headers are written relative to the scope of modules. All other authored documentation links are written relative to the page where the link is written.
 
-These relative documentation links can specify path components from higher up in the documentation hierarchy to reference container symbols or container pages. If a higher-up container page is shadowed by one of its descendants because they share the same name, the higher-up container page must be linked to using an absolute link.
+These relative documentation links can specify path components from higher up in the documentation hierarchy to reference container symbols or container pages. If a higher-up container page is shadowed by one of its descendants because they share the same name, the higher-up container page must be linked to using an absolute link or a sufficiently unambigious relative link.
 
 ```swift
 struct Container {
     struct Container {
         /// ``Container`` links to `Container.Container`
-        /// ``/MyModule/Container`` links to `Container`
+        /// ``MyModule/Container`` links to the outer `Container`
         func foo() { }
     }
 }
 ```
 
+> Note: If `MyModule` were to be named `Container` too, only the absolute link `/Container/Container` could be used to refer to the outer `Container`.
+
 ### Handling Ambiguous Links
 
 It's possible for collisions to occur in documentation links (symbol links or otherwise) where more than one page are represented by the same path. A common cause for documentation link collisions are function overloads (functions with the same name but different arguments or different return values). It's also possible to have documentation link collisions in conceptual content if an article file name is the same as a tutorial file name (excluding the file extension in both cases).