3) Keep heading punctuation as in the source. In particular, keep occurrences of literal « - » (space-hyphen-space) as « - » (the existing French docs use a hyphen here).

### French instructions about technical terms

    }

    @Keep
    protected void protectedOneArg(String s) {
      checkNotNull(s);
    }

    @Keep
    public void oneNullableArg(@Nullable String s) {}

    @Keep
    public void oneNullableArgThrows(@Nullable String s) {
      doThrow(s);
    }

    @Keep
    public void twoArg(String s, Integer i) {
      checkNotNull(s);
      i.intValue();
    }

    @Keep

### Target language

Translate to Japanese (日本語).

Language code: ja.

### Grammar and tone

1) Use polite, instructional Japanese (です/ます調).
2) Keep the tone concise and technical (match existing Japanese FastAPI docs).

### 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

### Quotes and punctuation

1) Keep punctuation style consistent with existing Traditional Chinese docs (they often mix English terms like “FastAPI” with Chinese text).
2) Never change punctuation inside inline code, code blocks, URLs, or file paths.
3) For more details, please follow the [Chinese Copywriting Guidelines](https://github.com/sparanoid/chinese-copywriting-guidelines).

### Ellipsis

import com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.NotTesterAnnotation;
import com.google.common.collect.testing.features.FeatureUtilTest.ExampleFeature.Require;
import com.google.errorprone.annotations.Keep;
import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.reflect.Method;
import java.util.Set;
import junit.framework.TestCase;

/**
 * @author George van den Driessche

For now we just have this global repository of ADRs.
If we see fit, we can break these out to per-platform ones, or keep a hybrid approach to having global and platform-specific ADSs.

Our aim is to keep the process lightweight and approachable.

        A proposal that works through the design along with the implications of the change can be opened as a KEP.
        See https://git.k8s.io/enhancements/keps#kubernetes-enhancement-proposals-keps
    validations:
      required: true

  - type: textarea
    id: rationale
    attributes:
      label: Why is this needed?
    validations:

    * This keeps the behavior consistent with Docker integration, and fixes an issue that some container Prometheus metrics don't work when there are summary stats for multiple instances of the same pod.

    }

    @Keep
    public static final class DeterministicRandom extends Random {
      @Keep
      public DeterministicRandom() {
        super(0);
      }
    }

    @Keep
    public static final class DummyScheduledThreadPoolExecutor extends ScheduledThreadPoolExecutor {
      @Keep
      public DummyScheduledThreadPoolExecutor() {
        super(1);
      }
    }

    @Keep

    A;

    @Keep
    public void failToCheckNull(String s) {}
  }

  private interface AnInterface {}

  private abstract static class AnAbstractClass {
    @Keep
    public AnAbstractClass(String s) {}

    @Keep
    public void failsToCheckNull(String s) {}
  }

  private static class NoPublicStaticMethods {
    @Keep // To test non-public factory isn't used.