diff --git a/text/1946-intra-rustdoc-links.md b/text/1946-intra-rustdoc-links.md
index 5ec2d42f6bf..8c85265e832 100644
--- a/text/1946-intra-rustdoc-links.md
+++ b/text/1946-intra-rustdoc-links.md
@@ -307,6 +307,8 @@ Our proposal is this:
   - It is possible that disambiguators for one kind of type-namespace object
     will work for the other (i.e. you can use `struct@` to refer to an enum),
     but do not rely on this.
+- Modules exist in both the type and value namespace and can be disambiguated
+  with a `mod@` or `module@`, e.g. `[module@foo]`
 - In links to macros,
   the link label can end with a `!`,
   e.g., `Look at the [FOO!] macro`. You can alternatively use a `macro@` prefix,
@@ -315,7 +317,7 @@ Our proposal is this:
   - Links to any kind of value (function, const, static) can be prefixed with `value@`,
     e.g., `See [value@foo]`.
   - Links to functions can be written with a `()` suffix,
-    e.g., `Also see the [foo()] function`. You can also use `function@`.
+    e.g., `Also see the [foo()] function`. You can also use `function@` or `fn@`.
   - Links to constants are prefixed with `const@`,
     e.g., `As defined in [const@FOO].`
   - Links to statics are prefixed with `static@`,