about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-10-01 07:36:35 -0700
committerbors <bors@rust-lang.org>2013-10-01 07:36:35 -0700
commit320af9b15723b10c31daa2e9fa8266486f4ba009 (patch)
treec6c8c36eff6d8eeccc68eae69ad7a3e18af97627
parent12404aaaddd1edc0c59e21f03a9f5ac8df828dcf (diff)
parent398e2c479a67ba0646b0c1ebde6ff0fac3f25522 (diff)
downloadrust-320af9b15723b10c31daa2e9fa8266486f4ba009.tar.gz
rust-320af9b15723b10c31daa2e9fa8266486f4ba009.zip
auto merge of #9645 : dckc/rust/patch-2, r=catamorphism
the switch from package `hello` to `pkg_id` is a little jarring; I'd use `<var>` but I don't see how. ALL_CAPS i.e. PKG_ID seems like a reasonable  poor-man's `<var>`.
-rw-r--r--doc/tutorial-rustpkg.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/tutorial-rustpkg.md b/doc/tutorial-rustpkg.md
index f1cf78fc630..156613cef4d 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