Doc review (#5475)

Author: lihaoyi

build.mill

@@ -68,9 +68,6 @@ def millLastTag: T[String] = Task {
 def millDownloadPrefix = Task {
   s"${Settings.mavenRepoUrl}/com/lihaoyi/mill-dist"
 }
-def millDownloadUrl = Task {
-  s"${millDownloadPrefix()}/${millLastTag()}"
-}
 
 def millDownloadUrlCurrent = Task {
   s"${millDownloadPrefix()}/${millVersion()}"

website/docs/modules/ROOT/pages/comparisons/why-mill.adoc

@@ -153,7 +153,7 @@ and makes all of them easy to set up and use.
 
 == Extensibility
 
-=== Builtins
+=== Rich Builtins
 
 Mill comes with a lot more functionality built in than other tools such as Maven,
 Gradle, or SBT. In general, most common development workflows are built in to Mill:
@@ -163,11 +163,15 @@ find plugins and evaluate their relevance, quality, and level of maintenance:
 
 include::partial$Feature_Support.adoc[]
 
-Apart from the builtin features, Mill also has a rich ecosystem of third party plugins
-for less common use cases:
+Mill's builtin functionality means you can get very far without spending time fiddling
+with plugins. These builtins are all designed, tested, and maintained to the same level of quality
+as Mill itself, letting you skip the tedious task of finding and vetting a list of third-party
+plugins of appropriate quality for use in your project.
 
-- xref::extending/thirdparty-plugins.adoc[]
+When the time comes that you do need functionality not bundled with Mill, Mill also has
+a rich ecosystem of third party plugins for less common use cases:
 
+- xref::extending/thirdparty-plugins.adoc[]
 
 === Extending Mill
 

website/docs/modules/ROOT/pages/index.adoc

@@ -9,16 +9,17 @@ in the JVM ecosystem:
 * Mill builds the same Java project xref:comparisons/why-mill.adoc#_performance[3-6x
  faster than Maven or Gradle] due to aggressive caching & parallelism
 
-* Mill builds require xref:comparisons/why-mill.adoc#_builtins[fewer plugins for common workflows],
+* Mill's xref:comparisons/why-mill.adoc#_object_oriented_builds[object-oriented builds] require
+xref:comparisons/why-mill.adoc#_rich_builtins[less fiddling with plugins]
 and are xref:comparisons/why-mill.adoc#_extending_mill[easier to extend with custom tasks]
 
 * Mill has better IDE support than other build tools, with
 xref:comparisons/why-mill.adoc#_ide_support[superior autocomplete and navigation in IntelliJ]
 
 Although the Java compiler is very fast and the Java language is easy to learn,
 JVM build tools have a reputation for being sluggish and confusing. Mill tries to
-offer a better alternative, its xref:comparisons/why-mill.adoc#_object_oriented_builds[object-oriented builds]
-letting your build system take full advantage of the Java platform's performance, usability, and IDE support.
+offer a better alternative, letting your build system take full advantage of the Java
+platform's performance, usability, and IDE support.
 
 If you prefer a video introduction to Mill, see:
 

website/package.mill

@@ -198,7 +198,7 @@ object `package` extends mill.Module {
       "main-branch",
       "main-branch",
       build.millLastTag(),
-      build.millDownloadUrl()
+      build.millDownloadUrlCurrent()
     )
     PathRef(dest)
   }