From: Rami Rosen <ramirose@gmail.com>
To: dts@dpdk.org
Cc: Rami Rosen <ramirose@gmail.com>
Subject: [dts] [PATCH] doc: fix typos in gsg/config
Date: Tue, 15 Jan 2019 20:16:09 +0200 [thread overview]
Message-ID: <20190115181609.3777-1-ramirose@gmail.com> (raw)
This patch fixes typos in dts_gsg/config.rst.
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
doc/dts_gsg/config.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/dts_gsg/config.rst b/doc/dts_gsg/config.rst
index 422a250..352b2ad 100644
--- a/doc/dts_gsg/config.rst
+++ b/doc/dts_gsg/config.rst
@@ -136,7 +136,7 @@ Debug interact support commands as below:
list(): list all connected sessions
connect(name): connect to session directly
exit(): exit dts
- quit(): quit debug mode and into noraml mode
+ quit(): quit debug mode and into normal mode
debug(): call python debug module
**--debugcase**
@@ -189,7 +189,7 @@ First of all, you must create a file named execution.cfg as below.
* test_suites: defines list of test suites, which will plan to be executed.
* targets: list of DPDK targets to be tested.
* parameters: you can define multiple keywords
-* scenario: Senario of DPDK virtualization environment for this execution.
+* scenario: Scenario of DPDK virtualization environment for this execution.
– nic_type : is the type of the NIC to use. The types are defined in the file settings.py.
There's one special type named as **cfg**, which mean network information will be loaded from file.
--
2.19.2
next reply other threads:[~2019-01-15 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 18:16 Rami Rosen [this message]
2019-01-16 6:13 ` Tu, Lijuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190115181609.3777-1-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).