From c0c1af497c15b70c48be17ab3411922886cdb679 Mon Sep 17 00:00:00 2001 From: Michael Gyarmathy Date: Wed, 13 Nov 2019 16:38:56 -0600 Subject: [PATCH] fix typo in processor-api developer guide docs --- docs/streams/developer-guide/processor-api.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/processor-api.html b/docs/streams/developer-guide/processor-api.html index ae33ebb78f23a..32951164868a4 100644 --- a/docs/streams/developer-guide/processor-api.html +++ b/docs/streams/developer-guide/processor-api.html @@ -195,7 +195,7 @@

implement your own custom store type. It’s common practice to leverage an existing store type via the Stores factory.

Note that, when using Kafka Streams, you normally don’t create or instantiate state stores directly in your code. - Rather, you define state stores indirectly by creating a so-called StoreBuilder. This buildeer is used by + Rather, you define state stores indirectly by creating a so-called StoreBuilder. This builder is used by Kafka Streams as a factory to instantiate the actual state stores locally in application instances when and where needed.

The following store types are available out of the box.