docs: Fix create memif cli

[vpp.git] / extras / libmemif / examples / example_setup_doc.md

diff --git a/extras/libmemif/examples/example_setup_doc.md b/extras/libmemif/examples/example_setup_doc.md
index 89a0b10..136477d 100644 (file)
--- a/extras/libmemif/examples/example_setup_doc.md
+++ b/extras/libmemif/examples/example_setup_doc.md
@@ -10,7 +10,7 @@ Run VPP and icmpr-epoll example (default example when running in container).
 
 VPP-side config:
 ```
-DBGvpp# create memif id 0 master
+DBGvpp# create interface memif id 0 master
 DBGvpp# set int state memif0/0 up
 DBGvpp# set int ip address memif0/0 192.168.1.1/24
 ```
@@ -18,7 +18,7 @@ icmpr-epoll:
 ```
 conn 0 0
 ```
-Memif in slave mode will try to connect every 2 seconds. If connection establishment is successfull, a message will show.
+Memif in slave mode will try to connect every 2 seconds. If connection establishment is successful, a message will show.
 ```
 INFO: memif connected!
 ```
@@ -187,7 +187,7 @@ Statistics: 5 sent, 4 received, 20% packet loss
 
 #### icmp_responder master icmp_responder slave
 
-> Example apps can only repond to ping. This setup creates connection between two applications using libmemif. Traffic functionality is the same as when connection to VPP. App can receive ARP/ICMP request and transmit response, but can not send ARP/ICMP request.
+> This setup creates connection between two applications using libmemif. Traffic functionality is the same as when connection to VPP. App can receive ARP/ICMP request and transmit response.
 
 Run two instances of icmpr-epoll example.
 > If not running in container, make sure folder /run/vpp/ exists before creating memif master.