From 398e2c479a67ba0646b0c1ebde6ff0fac3f25522 Mon Sep 17 00:00:00 2001 From: Dan Connolly Date: Mon, 30 Sep 2013 22:57:09 -0500 Subject: [PATCH] clarify that rust_pkg is a place-holder the switch from package `hello` to `rust_pkg` is a little jarring; I'd use but I don't see how. ALL_CAPS seems like a reasonable poor-man's . --- doc/tutorial-rustpkg.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/tutorial-rustpkg.md b/doc/tutorial-rustpkg.md index f1cf78fc63036..156613cef4d75 100644 --- a/doc/tutorial-rustpkg.md +++ b/doc/tutorial-rustpkg.md @@ -35,11 +35,11 @@ This makes sense, as we haven't gotten it from anywhere yet! Luckily for us, used like this: ~~~ {.notrust} -$ rustpkg install pkg_id +$ rustpkg install PKG_ID ~~~ -This will install a package named 'pkg_id' into your current Rust environment. -I called it 'pkg_id' in this example because `rustpkg` calls this a 'package +This will install a package named `PKG_ID` into your current Rust environment. +I called it `PKG_ID` in this example because `rustpkg` calls this a 'package identifier.' When using it with an external package like this, it's often a URI fragment. You see, Rust has no central authority for packages. You can build your own `hello` library if you want, and that's fine. We'd both host