This is an automated email from the ASF dual-hosted git repository.

zehnder pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/streampipes-website.git


The following commit(s) were added to refs/heads/dev by this push:
     new 5c2f5a7f3 Fix minor typos
5c2f5a7f3 is described below

commit 5c2f5a7f3b74ed50f85bcadd5294c4bec6572553
Author: Philipp Zehnder <[email protected]>
AuthorDate: Thu Oct 17 16:45:13 2024 +0200

    Fix minor typos
---
 docs/03_use-programmatically-create-adapters.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/03_use-programmatically-create-adapters.md 
b/docs/03_use-programmatically-create-adapters.md
index 5b38f79d3..d497d498e 100644
--- a/docs/03_use-programmatically-create-adapters.md
+++ b/docs/03_use-programmatically-create-adapters.md
@@ -5,7 +5,7 @@ sidebar_label: Adapters as Code
 ---
 
 In Apache StreamPipes, adapters are typically created via the web interface. 
-However, it is possible to create adapters programmatically using a compact 
YAML format and the treamPipes REST API. 
+However, it is possible to create adapters programmatically using a compact 
YAML format and the StreamPipes REST API. 
 Programmatic creation of adapters can be a useful feature in cases where many 
similar adapters have to be created. 
 In this case, an externally managed YAMl file containing the full adapter 
configuration can be used and modified.
 
@@ -73,7 +73,7 @@ Here is a walkthrough to create an adapter programmatically 
over the API:
 
 ### Background: Internal adapter generation process
 
-The YAML definition file is a more compact notation of StreamPipes' internal 
data format to represent an adapter.
+The YAML definition file is a more compact notation of StreamPipes internal 
data format to represent an adapter.
 When creating an adapter over the user interface, StreamPipes requires some 
basic, adapter-specific settings.
 Afterwards, a `Guess Schema` step is executed. In this step, StreamPipes 
connects to the underlying data sources, receives some samples of live data, 
determines the exact schema of the data stream and provides user with the 
source schema.
 This schema can be further refined using `Transformation Rules`. 

Reply via email to