_content/doc/modules: fix incorrect require directive in modules doc

As pointed out in golang/go#70747, the version in the require directive should not include the nested module directory. Fixes golang/go#70747 Change-Id: I3a04fe928ac744194d7a271acb1aff8e3610ae6f Reviewed-on: https://go-review.googlesource.com/c/website/+/635280 LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Robert Findley <[email protected]> Reviewed-by: Peter Weinberger <[email protected]>
golang · Dec 12, 2024 · ce4f609 · ce4f609
1 parent 278ac22
commit ce4f609
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/_content/doc/modules/managing-source.md b/_content/doc/modules/managing-source.md
@@ -160,7 +160,7 @@ the following for version v1.2.3:
 *   Module path: `example.com/mymodules/module1`
 *   Version tag: `module1/v1.2.3`
 *   Package path imported by a user: `example.com/mymodules/module1/package1`
-*   Module path as given in a user's require directive: `example.com/mymodules/module1 module1/v1.2.3`
+*   Module path and version as specified in a user's require directive: `example.com/mymodules/module1 v1.2.3`
 
 <img src="images/multiple-modules.png"
      alt="Diagram illustrating two modules in a single repository"