anchor.diff:  <2> An initializer method must be annotated with `@Inject`. 
   <3> An initializer may accept multiple parameters - each one is an injection point.
   
  -== _Q: You talked about some qualifiers?_
  -
  -A: https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#qualifiers[Qualifiers, window="_blank"] are annotations that help the container to distinguish beans that implement the same type.
  +== You talked about some qualifiers?
  +
  +https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#qualifiers[Qualifiers, window="_blank"] are annotations that help the container to distinguish beans that implement the same type.
   As we already said a bean is assignable to an injection point if it has all the required qualifiers.
   If you declare no qualifier at an injection point the `@Default` qualifier is assumed.
   
  
positive.code: You can declare qualifiers, inject dependencies into the producer methods parameters, etc. 
  You can read more about producers for example in the https://docs.jboss.org/weld/reference/latest/en-US/html/producermethods.html[Weld docs, window="_blank"].
  
  == _Q: OK, injection looks cool. What other services are provided?_
  
  === Lifecycle Callbacks
  
  
negative.code: Therefore, we recommend to stick with `@ApplicationScoped` by default unless there's a good reason to use `@Singleton`.
  
  [[client_proxies]]
  == I don't understand the concept of client proxies.
  
  Indeed, the https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#client_proxies[client proxies, window="_blank"] could be hard to grasp but they provide some useful functionality.
  A client proxy is basically an object that delegates all method invocations to a target bean instance.
  It's a container construct that implements `io.quarkus.arc.ClientProxy` and extends the bean class.
  
  