You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by ot...@apache.org on 2020/03/05 12:17:50 UTC

[plc4x] branch develop updated: Update general-concepts.adoc

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

otluk pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git


The following commit(s) were added to refs/heads/develop by this push:
     new 65fae08  Update general-concepts.adoc
65fae08 is described below

commit 65fae082edb91c010ceb66454df8e257fbec6a3b
Author: ottlukas <ot...@gmail.com>
AuthorDate: Thu Mar 5 13:17:40 2020 +0100

    Update general-concepts.adoc
---
 src/site/asciidoc/users/plc4j/general-concepts.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/asciidoc/users/plc4j/general-concepts.adoc b/src/site/asciidoc/users/plc4j/general-concepts.adoc
index 0a4106c..9067ac4 100644
--- a/src/site/asciidoc/users/plc4j/general-concepts.adoc
+++ b/src/site/asciidoc/users/plc4j/general-concepts.adoc
@@ -54,7 +54,7 @@ The Serial Port transport simply reads and writes data to a given serial port.
 
 The probably most special forms of transport are currently the `PCAP replay` and the `Test` transport.
 
-The `PCAP replay` transport allows recording network traffic using tools like `WreShark` and to simply replay these recorded `pcap` and `pcapng` files. This is really helpful for writing new drivers (especially passive mode drivers) without having to be connected to the real device.
+The `PCAP replay` transport allows recording network traffic using tools like `WireShark` and to simply replay these recorded `pcap` and `pcapng` files. This is really helpful for writing new drivers (especially passive mode drivers) without having to be connected to the real device.
 
 From a driver point of view there is actually no difference between a `Raw Socket` and a `PCAP replay` transport.
 
@@ -102,4 +102,4 @@ Then this shorter version can be used. Please inspect the `Protocol Documentatio
 
 Addresses are extremely dependent on the used protocol, as we usually decided to stick to the address formats that are used in that particular environments.
 
-Please check the `Protocol Documentation` on details about these address formats.
\ No newline at end of file
+Please check the `Protocol Documentation` on details about these address formats.