[#259] small doc fixes for @Inject

docs/index.adoc

@@ -2302,7 +2302,7 @@ Usage: <main class>
 Custom handlers can extend `AbstractHandler` to inherit this behaviour.
 
 === `@Inject` Annotation
-Picocli 3.2 introduces a custom `@Inject` annotation (not `javax.inject.Inject`) for injecting the `CommandSpec` model of the command into a command field.
+Picocli 3.2 introduces a custom `@Inject` annotation (`picocli.CommandLine.Inject`, not `javax.inject.Inject`) for injecting the `CommandSpec` model of the command into a command field.
 
 This is useful when a command needs to use the picocli API, for example to walk the command hierarchy and iterate over its sibling commands.
 This complements the `@ParentCommand` annotation;  the `@ParentCommand` annotation injects a user-defined command object, whereas this annotation injects a picocli class.

src/main/java/picocli/CommandLine.java

@@ -2183,11 +2183,10 @@ private static class NoCompletionCandidates implements Iterable<String> {
         String name() default "";
     }
     /**
-     * Fields annotated with {@code @Inject} will be initialized with the {@code CommandLine} or {@code CommandSpec} for the command the field is part of. Example usage:
+     * Fields annotated with {@code @Inject} will be initialized with the {@code CommandSpec} for the command the field is part of. Example usage:
      * <pre>
      * class InjectExample implements Runnable {
-     *     &#064;Inject CommandLine commandLine; // usually you inject either the CommandLine
-     *     &#064;Inject CommandSpec commandSpec; // or the CommandSpec
+     *     &#064;Inject CommandSpec commandSpec;
      *     //...
      *     public void run() {
      *         // do something with the injected objects