From c06b4e46c90fa45033d0433e0a9943358d2bc337 Mon Sep 17 00:00:00 2001 From: Dariusz Sosnowski Date: Fri, 29 Oct 2021 16:19:02 +0300 Subject: [PATCH] doc: fix typo in coding style [ upstream commit 6965091e0bf15134328ed0038b03a7700dc17245 ] This patch fixes a typo in DPDK Coding Style, in Return Values section, i.e. replaces "indicated may" with "indicated by". Fixes: 36032e46be40 ("doc: add coding style") Signed-off-by: Dariusz Sosnowski Acked-by: Bruce Richardson --- doc/guides/contributing/coding_style.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/contributing/coding_style.rst b/doc/guides/contributing/coding_style.rst index 841ef6d5c8..95e2d4c22c 100644 --- a/doc/guides/contributing/coding_style.rst +++ b/doc/guides/contributing/coding_style.rst @@ -591,7 +591,7 @@ Return Value ~~~~~~~~~~~~ * Functions which create objects, or allocate memory, should return pointer types, and NULL on error. - The error type should be indicated may setting the variable ``rte_errno`` appropriately. + The error type should be indicated by setting the variable ``rte_errno`` appropriately. * Functions which work on bursts of packets, such as RX-like or TX-like functions, should return the number of packets handled. * Other functions returning int should generally behave like system calls: returning 0 on success and -1 on error, setting ``rte_errno`` to indicate the specific type of error.