=doc Fix indefinite articles typos in docs (#20924)
This commit is contained in:
parent
9e6f346a19
commit
1009f8e235
10 changed files with 13 additions and 13 deletions
|
|
@ -281,7 +281,7 @@ Actors may also use a Camel `ProducerTemplate`_ for producing messages to endpoi
|
|||
|
||||
.. includecode:: code/docs/camel/MyActor.java#ProducerTemplate
|
||||
|
||||
For initiating a a two-way message exchange, one of the
|
||||
For initiating a two-way message exchange, one of the
|
||||
``ProducerTemplate.request*`` methods must be used.
|
||||
|
||||
.. includecode:: code/docs/camel/RequestBodyActor.java#RequestProducerTemplate
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ of an HTTP request or response (depending on whether used on the client or serve
|
|||
Marshalling
|
||||
-----------
|
||||
|
||||
On the server-side marshalling is used to convert a application-domain object to a response (entity). Requests can
|
||||
On the server-side marshalling is used to convert an application-domain object to a response (entity). Requests can
|
||||
contain an ``Accept`` header that lists acceptable content types for the client. A marshaller contains the logic to
|
||||
negotiate the result content types based on the ``Accept`` and the ``AcceptCharset`` headers.
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ These marshallers are provided by akka-http:
|
|||
Unmarshalling
|
||||
-------------
|
||||
|
||||
On the server-side unmarshalling is used to convert a request (entity) to a application-domain object. This is done
|
||||
On the server-side unmarshalling is used to convert a request (entity) to an application-domain object. This is done
|
||||
in the ``MarshallingDirectives.request`` or ``MarshallingDirectives.entity`` directive. There are several unmarshallers
|
||||
provided by akka-http:
|
||||
|
||||
|
|
|
|||
|
|
@ -138,7 +138,7 @@ Finally, there are two methods available for convenience to complete the stage a
|
|||
|
||||
|
||||
In some cases it is inconvenient and error prone to react on the regular state machine events with the
|
||||
signal based API described above. For those cases there is a API which allows for a more declarative sequencing
|
||||
signal based API described above. For those cases there is an API which allows for a more declarative sequencing
|
||||
of actions which will greatly simplify some use cases at the cost of some extra allocations. The difference
|
||||
between the two APIs could be described as that the first one is signal driven from the outside, while this API
|
||||
is more active and drives its surroundings.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ For more advanced use cases the :class:`ActorPublisher` and :class:`ActorSubscri
|
|||
provided to support implementing Reactive Streams :class:`Publisher` and :class:`Subscriber` with
|
||||
an :class:`Actor`.
|
||||
|
||||
These can be consumed by other Reactive Stream libraries or used as a
|
||||
These can be consumed by other Reactive Stream libraries or used as an
|
||||
Akka Streams :class:`Source` or :class:`Sink`.
|
||||
|
||||
.. warning::
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue