*   <li>An IPv6 address string with or without brackets, like {@code [2001:db8::1]} or {@code
   *       2001:db8::1}
   * </ul>
   *
   * @throws IllegalArgumentException if the specifier is not valid.
   */
  public static HostSpecifier fromValid(String specifier) {
    // Verify that no port was specified, and strip optional brackets from
    // IPv6 literals.

As the type, put `list`.

As the list is a type that contains some internal types, you put them in square brackets:

{* ../../docs_src/python_types/tutorial006_py39.py hl[1] *}

/// info

Those internal types in the square brackets are called "type parameters".

In this case, `str` is the type parameter passed to `list`.

///

### Headings

1) Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
2) Do not add a trailing period at the end of headings.

### Quotes

1) Prefer Japanese corner brackets 「」 in normal prose when quoting a term.
2) Do not change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

1) Keep ellipsis style consistent with existing Japanese docs (commonly `...`).

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a

        «««
        ## Typhinweise und –annotationen { #type-hints-and-annotations }
        »»»

3.2) Do not apply rule 3 to the untranslated part of the heading inside curly brackets, which you shall not translate.


### German instructions, when to use and when not to use hyphens in words (written in first person, which is you)

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a

                .forEach(file -> {
                    try {
                        // The regex `^\\s*\\[\\[(.*)\\]\\]` looks for lines starting with '[[...]]'
                        // and captures the content within the brackets.
                        Files.readAllLines(file).forEach(line -> {
                            if (line.matches("^\\s*\\[\\[(.*)\\]\\].*")) {