chore(docs): Emphasize the "may" bit of the backpressure docs (vector…

…dotdev#18457) Since not all sources, including the `http_server` source, do actually handle back-pressure in the described ways yet. This confused a user that was expecting that the `http_server` source would be returning 429s in the precense of back-pressure. Signed-off-by: Jesse Szwedko <[email protected]>
aholmberg · Sep 1, 2023 · 1647964 · 1647964
1 parent 40ef7c4
commit 1647964
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/website/content/en/docs/about/concepts.md b/website/content/en/docs/about/concepts.md
@@ -80,8 +80,8 @@ View the full configuration options for buffers [here](/docs/reference/configura
 
 If a sink's buffer fills up and is configured to provide backpressure, that backpressure will propagate to any connected
 transforms, which will also propagate to the sources. The sources attempt to propagate backpressure to
-whichever system is providing data. The exact mechanism varies with the source. For example, HTTP sources may
-reject requests with an HTTP 429 error (Too Many Requests), or pull-based sources such as Kafka may slow down fetching new events.
+whichever system is providing data. The exact mechanism varies with the source. For example, HTTP sources _may_
+reject requests with an HTTP 429 error (Too Many Requests), or pull-based sources such as Kafka _may_ slow down fetching new events.
 
 Since Vector allows configuring components as a directed acyclic graph, understanding how backpressure works when there
 are multiple sinks or sources involved is important.