add a name: and mark it as required

src/site/docs/pub-package-manager/pubspec.markdown

Index: src/site/docs/pub-package-manager/pubspec.markdown
diff --git a/src/site/docs/pub-package-manager/pubspec.markdown b/src/site/docs/pub-package-manager/pubspec.markdown
index 12f437d3253c066b6ad9c615d156836e49386cff..b5a2caa91ec11f967b8c03ba50bb34b1f8ff2cd4 100644
--- a/src/site/docs/pub-package-manager/pubspec.markdown
+++ b/src/site/docs/pub-package-manager/pubspec.markdown
@@ -29,7 +29,7 @@ dependencies:
 
 ## Name
 
-Every package needs a name. When your stellar code gets props on the world
+**Required**: every package needs a name. When your stellar code gets props on the world

[Bob Nystrom, 2012/08/29 17:47:32]

This seems a bit ugly to me. Is it really necessary?

[sethladd, 2012/08/29 19:49:18]

I care less about how we format this, but when I look at this as technical
documentation, we need to specify what is required and what is optional (in a
clear and concise way)

I'm open to how to say "required" in clear way. Ideas? Maybe a table of fields,
marked with required and optional?

This is great commentary, but also useful is the technical conciseness.

[Bob Nystrom, 2012/08/29 19:53:50]

Right now, there are only three fields, and one of them is required so I don't
know if we're quite ready for a table yet. But we will be adding more metadata
relatively soon. How about we iterate on this then?

[sethladd, 2012/08/29 20:01:41]

I changed it a bit in the latest patch. I think a table would be fine now,
actually, but it's not a big deal.

I can image:

field, required, type (num, strong, bool), format, notes

Also, this is the kind of thing we can do for you after things settle down a
little.

 stage, this is what they'll be hollering. Also, it's how other packages will
 refer to yours, and how it will appear on [pub.dartlang.org][pubsite], should
 you publish it.
@@ -45,7 +45,11 @@ save you heartache later.
 
 ## Version
 
-Every package has a version. No one really gets excited about versioning, but
+Every package has a version. A version number is required to host your package on

[Bob Nystrom, 2012/08/29 17:47:32]

Long line.

[sethladd, 2012/08/29 19:49:18]

Done.

+[pub.dartlang.org][pubsite], but can be omitted for local-only packages. If you
+omit it, your package is implicitly versioned `0.0.0`.
+
+No one really gets excited about versioning, but
 it's a necessary evil for reusing code while letting it evolve quickly. A
 version number is three numbers separated by dots, like `0.2.43`. It can also
 optionally have a build (`+hotfix.oopsie`) or pre-release (`-alpha.12`) suffix.
@@ -60,10 +64,6 @@ yourself for hordes of angry users.
 
 [semantic versioning]: http://semver.org
 
-A version number is required to host your package on
-[pub.dartlang.org][pubsite], but can be omitted for local-only packages. If you
-omit it, your package is implicitly versioned `0.0.0`.
-
 ## Description
 
 This is optional for your own personal packages, but if you intend to share