From 0f2f5671d73814f327353c019c5758bd87d1db6d Mon Sep 17 00:00:00 2001 From: knative-automation Date: Thu, 14 Jan 2021 23:53:20 -0800 Subject: [PATCH] Format markdown (#4746) Signed-off-by: Knative Automation --- docs/spec/data-plane.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/spec/data-plane.md b/docs/spec/data-plane.md index 377e096317a..3d99419c4ac 100644 --- a/docs/spec/data-plane.md +++ b/docs/spec/data-plane.md @@ -94,17 +94,17 @@ CloudEvents received by Sink MAY have ### Event reply contract An event sender supporting event replies SHOULD include a `Prefer: reply` header -in delivery requests to indicate to the sink that event reply is supported. An event -sender MAY ignore an event reply in the delivery response if the `Prefer: reply` -header was not included in the delivery request. - -An example is that a Broker supporting event reply sends events with an additional header -`Prefer: reply` so that the sink connected to the Broker knows event replies will -be accepted. While a source sends events without the header, in which case the sink may -assume that any event reply will be dropped without error or retry attempt. If a sink -wishes to ensure the reply events will be delivered, it can check for the existence of -the `Prefer: reply` header in the delivery request and respond with an error code -if the header is not present. +in delivery requests to indicate to the sink that event reply is supported. An +event sender MAY ignore an event reply in the delivery response if the +`Prefer: reply` header was not included in the delivery request. + +An example is that a Broker supporting event reply sends events with an +additional header `Prefer: reply` so that the sink connected to the Broker knows +event replies will be accepted. While a source sends events without the header, +in which case the sink may assume that any event reply will be dropped without +error or retry attempt. If a sink wishes to ensure the reply events will be +delivered, it can check for the existence of the `Prefer: reply` header in the +delivery request and respond with an error code if the header is not present. ### Data plane contract for Sources