Duplicate documentation blocks in publishing docs

[arturaz]

From https://mill-build.org/mill/main-branch/javalib/publishing.html:

publishLocal accepts options like --doc=false and --sources=false, to disable publishing javadoc JARs and source JARs, which are generated and published by default. This can be helpful if you’re not interested in javadoc JARs, and javadoc generation fails, and you would rather address those errors later for example.

publishLocal also accepts --transitive=true, to also publish locally the transitive dependencies of the module being published. This ensures the module can be resolved from the local repository, with no missing dependencies.

publishLocal publishes the artifacts to the ~/.ivy2/local folder on your machine, allowing them to be resolved by other projects and build tools. This is useful as a lightweight way of testing out the published artifacts, without the setup overhead and long latencies of publishing artifacts globally accessible to anyone in the world.

publishLocal accepts options like --doc=false and --sources=false, to disable publishing javadoc JARs and source JARs, which are generated and published by default. This can be helpful if you’re not interested in javadoc JARs, and javadoc generation fails or takes too much time. When using Scala 2, disabling javadoc generation can bring large speedups, given it entails compiling your code a second time.

publishLocal also accepts --transitive=true, to also publish locally the transitive dependencies of the module being published. This ensures the module can be resolved from the local repository, with no missing dependencies.

Seems like one of those is coming from

mill/example/javalib/publishing/2-publish-module/build.mill

Lines 31 to 38 in ac14db4

	// `publishLocal` accepts options like `--doc=false` and `--sources=false`,
	// to disable publishing javadoc JARs and source JARs, which are generated and
	// published by default. This can be helpful if you're not interested in javadoc JARs,
	// and javadoc generation fails, and you would rather address those errors later for example.
	// `publishLocal` also accepts `--transitive=true`, to also publish locally the
	// transitive dependencies of the module being published. This ensures the module
	// can be resolved from the local repository, with no missing dependencies.

Whilst another one from

mill/example/scalalib/publishing/2-publish-module/build.mill

Lines 42 to 51 in ac14db4

	// `publishLocal` accepts options like `--doc=false` and `--sources=false`,
	// to disable publishing javadoc JARs and source JARs, which are generated and
	// published by default. This can be helpful if you're not interested in javadoc JARs,
	// and javadoc generation fails or takes too much time. When using Scala 2, disabling
	// javadoc generation can bring large speedups, given it entails compiling your code
	// a second time.
	// `publishLocal` also accepts `--transitive=true`, to also publish locally the
	// transitive dependencies of the module being published. This ensures the module
	// can be resolved from the local repository, with no missing dependencies.