Docu: correct several links after renaming default branch (master to main)

README.md

@@ -72,7 +72,7 @@ implement [custom parameter processing](https://picocli.info/#_custom_parameter_
 
 Picocli-based applications can easily [integrate](https://picocli.info/#_dependency_injection) with Dependency Injection containers.
 The [Micronaut](https://micronaut.io/) microservices framework has [built-in support](https://docs.micronaut.io/latest/guide/index.html#commandLineApps) for picocli.
-Picocli ships with a [`picocli-spring-boot-starter` module](https://github.com/remkop/picocli/tree/master/picocli-spring-boot-starter)
+Picocli ships with a [`picocli-spring-boot-starter` module](https://github.com/remkop/picocli/tree/main/picocli-spring-boot-starter)
 that includes a `PicocliSpringFactory` and Spring Boot auto-configuration to use Spring dependency injection in your picocli command line application.
 The user manual has examples of integrating with [Guice](https://picocli.info/#_guice_example), [Spring Boot](https://picocli.info/#_spring_boot_example), [Micronaut](https://picocli.info/#_micronaut_example), [Quarkus](https://picocli.info/#_quarkus_example) and with containers that comply to [CDI 2.0 specification](https://picocli.info/#_cdi_2_0_jsr_365) (JSR 365).
 
@@ -196,7 +196,7 @@ Join the [picocli Google group](https://groups.google.com/d/forum/picocli) if yo
 
 ### Commitments
 
-| This project follows [semantic versioning](http://semver.org/) and adheres to the **[Zero Bugs Commitment](https://github.com/classgraph/classgraph/blob/master/Zero-Bugs-Commitment.md)**. |
+| This project follows [semantic versioning](http://semver.org/) and adheres to the **[Zero Bugs Commitment](https://github.com/classgraph/classgraph/blob/latest/Zero-Bugs-Commitment.md)**. |
 |------------------------|
 
 ## Adoption
@@ -245,7 +245,7 @@ Join the [picocli Google group](https://groups.google.com/d/forum/picocli) if yo
 * Picocli is used in the Apache Hadoop Ozone/HDDS command line tools, the Apache Hive benchmark CLI, Apache [Ignite TensorFlow](https://github.com/apache/ignite), and Apache Sling [Feature Model Converter](https://github.com/apache/sling-org-apache-sling-feature-modelconverter).
 * Picocli is listed on [StackShare](https://stackshare.io/picocli). Please add it to your stack and add/upvote reasons why you like picocli!
 * Picocli is used in Pinterest [ktlint](https://ktlint.github.io/).
-* Picocli is used in Spring IO [nohttp-cli](https://github.com/spring-io/nohttp/tree/master/nohttp-cli).
+* Picocli is used in Spring IO [nohttp-cli](https://github.com/spring-io/nohttp/tree/main/nohttp-cli).
 * The [MinecraftPicocli](https://github.com/Rubydesic/MinecraftPicocli) library facilitates the use of picocli in [Minecraft Forge](https://files.minecraftforge.net/).
 * [Simple Java Mail](http://www.simplejavamail.org/) now offers a picocli-based [CLI](http://www.simplejavamail.org/cli.html#navigation).
 * [jbang](https://github.com/maxandersen/jbang) not only uses picocli internally, but also has a CLI template to generate an initial script: use `jbang --init=cli helloworld.java` to generate a sample picocli-enabled jbang script. See [asciinema](https://asciinema.org/a/AVwA19yijKRNKEO0bJENN2ME3?autoplay=true&speed=2).
@@ -352,11 +352,11 @@ For example, your application can generate help like this with a custom layout:
 
 ![Usage help message with two options per row](docs/images/UsageHelpWithCustomLayout.png?raw=true)
 
-See the [source code](https://github.com/remkop/picocli/blob/master/src/test/java/picocli/CustomLayoutDemo.java#L61).
+See the [source code](https://github.com/remkop/picocli/blob/main/src/test/java/picocli/CustomLayoutDemo.java#L61).
 
 ## Download
 You can add picocli as an external dependency to your project, or you can include it as source.
-See the [source code](https://github.com/remkop/picocli/blob/master/src/main/java/picocli/CommandLine.java). Copy and paste it into a file called `CommandLine.java`, add it to your project, and enjoy!
+See the [source code](https://github.com/remkop/picocli/blob/main/src/main/java/picocli/CommandLine.java). Copy and paste it into a file called `CommandLine.java`, add it to your project, and enjoy!
 
 ### Gradle
 ```

RELEASE-NOTES.md

@@ -1799,7 +1799,7 @@ Picocli follows [semantic versioning](http://semver.org/).
 This release adds a new class `picocli.codegen.docgen.manpage.ManPageGenerator` to the `picocli-codegen` module that generates AsciiDoc documentation for picocli-based applications using the `manpage` doctype and manpage document structure.
 The generated AsciiDoc files can be converted to HTML, PDF and unix man pages with the [asciidoctor](https://asciidoctor.org/docs/user-manual/#man-pages) tool.
 
-The [`picocli-codegen` README](https://github.com/remkop/picocli/blob/master/picocli-codegen/README.adoc) has more details.
+The [`picocli-codegen` README](https://github.com/remkop/picocli/blob/main/picocli-codegen/README.adoc) has more details.
 
 ### <a name="4.2.0-repeatable-subcommands"></a> Repeatable Subcommands
 From picocli 4.2, it is possible to specify that a command's subcommands can be specified multiple times by marking it with `@Command(subcommandsRepeatable = true)`.
@@ -2125,7 +2125,7 @@ JLine has had some interesting improvements in its 3.12 release.
 
 This version of picocli requires JLine 3.13.2 or higher and adds a `PicocliCommands` class that provides command descriptions that can be displayed in the terminal status bar via the new JLine `TailTipWidgets` functionality.
 
-See the `picocli-shell-jline3` [README](https://github.com/remkop/picocli/tree/master/picocli-shell-jline3) for details.
+See the `picocli-shell-jline3` [README](https://github.com/remkop/picocli/tree/main/picocli-shell-jline3) for details.
 
 ### <a name="4.1.2-completion"></a> Completion
 The built-in `picocli.AutoComplete.GenerateCompletion` (`generate-completion`) subcommand now omits validation of mandatory options in the parent command.
@@ -2598,7 +2598,7 @@ In most cases no further configuration is needed when generating a native image.
 
 #### Processor option: `project`
 
-The picocli annotation processor supports a number of [options](https://github.com/remkop/picocli/tree/master/picocli-codegen#picocli-processor-options), most important of which is the `project` option to control the output subdirectory: the generated files are written to `META-INF/native-image/picocli-generated/${project}`. A good convention is to use the Maven `${groupId}/${artifactId}` as the value; a unique subdirectory ensures your jar can be shaded with other jars that may also contain generated configuration files.
+The picocli annotation processor supports a number of [options](https://github.com/remkop/picocli/tree/main/picocli-codegen#picocli-processor-options), most important of which is the `project` option to control the output subdirectory: the generated files are written to `META-INF/native-image/picocli-generated/${project}`. A good convention is to use the Maven `${groupId}/${artifactId}` as the value; a unique subdirectory ensures your jar can be shaded with other jars that may also contain generated configuration files.
 
 To configure this option, pass the `-Aproject=<some value>` to the javac compiler. The examples below show how to do this for Maven and Gradle.
 
@@ -2633,7 +2633,7 @@ In Maven, use `annotationProcessorPaths` in the `configuration` of the `maven-co
 </plugin>
 ```
 
-See the [`picocli-codegen` README](https://github.com/remkop/picocli/tree/master/picocli-codegen) for more details.
+See the [`picocli-codegen` README](https://github.com/remkop/picocli/tree/main/picocli-codegen) for more details.
 
 
 ##### Gradle
@@ -2653,7 +2653,7 @@ compileJava {
 }
 ```
 
-See the [`picocli-codegen` README](https://github.com/remkop/picocli/tree/master/picocli-codegen) for more details.
+See the [`picocli-codegen` README](https://github.com/remkop/picocli/tree/main/picocli-codegen) for more details.
 
 
 
@@ -4890,7 +4890,7 @@ This release contains the `picocli.shell.jline3.PicocliJLineCompleter` class.
 `PicocliJLineCompleter` is a small component that generates completion candidates to allow users to get command line TAB auto-completion for a picocli-based application running in a JLine 3 shell.
 It is similar to the class with the same name in the `picocli.shell.jline2` package in the `picocli-shell-jline2` module.
 
-See the module's [README](https://github.com/remkop/picocli/blob/master/picocli-shell-jline3/README.md) for more details.
+See the module's [README](https://github.com/remkop/picocli/blob/main/picocli-shell-jline3/README.md) for more details.
 
 ### <a name="3.9.0-ANSI-heuristics"></a> Improved ANSI Heuristics
 This release has improved heuristics to decide whether ANSI escape codes should be emitted or not.
@@ -5171,7 +5171,7 @@ The output of `ReflectionConfigGenerator` is intended to be passed to the `-H:Re
 
 See [Picocli on GraalVM: Blazingly Fast Command Line Apps](https://github.com/remkop/picocli/wiki/Picocli-on-GraalVM:-Blazingly-Fast-Command-Line-Apps) for details.
 
-The module's [README](https://github.com/remkop/picocli/blob/master/picocli-codegen/README.md) explains how to configure your build to generate the configuration file automatically as part of your build.
+The module's [README](https://github.com/remkop/picocli/blob/main/picocli-codegen/README.md) explains how to configure your build to generate the configuration file automatically as part of your build.
 
 
 ### <a name="3.7.0-picocli-shell-jline2"></a> New Module `picocli-shell-jline2`
@@ -5182,7 +5182,7 @@ This release contains the `PicocliJLineCompleter` class.
 `PicocliJLineCompleter` is a small component that generates completion candidates to allow users to
 get command line TAB auto-completion for a picocli-based application running in a JLine 2 shell.
 
-See the module's [README](https://github.com/remkop/picocli/blob/master/picocli-shell-jline2/README.md) for more details.
+See the module's [README](https://github.com/remkop/picocli/blob/main/picocli-shell-jline2/README.md) for more details.
 
 ## <a name="3.7.0-fixes"></a> Fixed issues
 - [#503] Build: Upgrade to gradle 4.10.2.
@@ -7698,7 +7698,7 @@ public interface IVersionProvider {
 }
 ```
 
-The GitHub project has a manifest file-based [example](https://github.com/remkop/picocli/blob/master/examples/src/main/java/picocli/examples/VersionProviderDemo2.java) and a build-generated version properties file-based [example](https://github.com/remkop/picocli/blob/master/examples/src/main/java/picocli/examples/VersionProviderDemo1.java) version provider implementation.
+The GitHub project has a manifest file-based [example](https://github.com/remkop/picocli/blob/main/examples/src/main/java/picocli/examples/VersionProviderDemo2.java) and a build-generated version properties file-based [example](https://github.com/remkop/picocli/blob/main/examples/src/main/java/picocli/examples/VersionProviderDemo1.java) version provider implementation.
 
 ### Custom factory
 Declaratively registered subcommands, type converters and version providers must be instantiated somehow. From this release, a custom factory can be specified when constructing a `CommandLine` instance. This allows full control over object creation and opens possibilities for Inversion of Control and Dependency Injection. For example:

docs/announcing-picocli-1.0.adoc

@@ -27,7 +27,7 @@ Let's look at how picocli tries to address these issues.
 
 How often have you chosen to write custom code to parse command line arguments instead of using a library because you didn’t want to burden your users with the extra dependency?
 
-Picocli offers a way to let users run picocli-based applications without requiring the picocli library as an external dependency: all the source code lives in a https://github.com/remkop/picocli/blob/master/src/main/java/picocli/CommandLine.java[single file], to encourage application authors to include it in source form. This is convenient for utility-like single-jar applications.
+Picocli offers a way to let users run picocli-based applications without requiring the picocli library as an external dependency: all the source code lives in a https://github.com/remkop/picocli/blob/main/src/main/java/picocli/CommandLine.java[single file], to encourage application authors to include it in source form. This is convenient for utility-like single-jar applications.
 
 There are other ways to accomplish this, like JAR shading, but this is an alternative. It is easy to understand, easy to do, and it doesn’t require any special tooling. Application authors can upgrade to newer versions of picocli by replacing a single source file.
 

docs/autocomplete.adoc

@@ -423,7 +423,7 @@ Star icon:star-o[] or fork icon:code-fork[] this project on GitHub if you like i
 Please use the https://github.com/remkop/picocli/issues[Issue Tracker] to report bugs or request features.
 
 == License
-Picocli is licensed under the https://github.com/remkop/picocli/blob/master/LICENSE[Apache License 2.0].
+Picocli is licensed under the https://github.com/remkop/picocli/blob/main/LICENSE[Apache License 2.0].
 
 == Releases
 Previous versions are available from the GitHub project https://github.com/remkop/picocli/releases[Releases].

docs/feedback.adoc

@@ -122,7 +122,7 @@ picocli便利でした! / KuromojiのCLIコマンドとpicocliとGraalVM-
 [quote, wreulicke (@wreulicke), https://twitter.com/wreulicke/status/1232488166910648321]
 picocliならspring-boot-starterもあるので
 spring bootとのintegrationも簡単ですね
-https://github.com/remkop/picocli/tree/master/picocli-spring-boot-starter
+https://github.com/remkop/picocli/tree/main/picocli-spring-boot-starter
 
 ---
 [quote, Eduardo Gonzalez (@wm_eddie), https://twitter.com/wm_eddie/status/1228302473032429568]