From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 2/2] doc: ref_make_macros: improve language, typos and markup
Date: Wed, 5 Jun 2019 17:20:31 +0200 [thread overview]
Message-ID: <20190605152031.17474-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20190605152031.17474-1-rhi@pengutronix.de>
The literal blocks don't need to be code-blocks, as there is no code to
be highlighted.
Turn down the inline markup to make the text better readable. A
technical term doesn't need to be emphasized every time it occurs.
Use semantic newlines where applicable.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
doc/ref_make_macros.inc | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/doc/ref_make_macros.inc b/doc/ref_make_macros.inc
index 749cf31edf66..5bef79f44d00 100644
--- a/doc/ref_make_macros.inc
+++ b/doc/ref_make_macros.inc
@@ -44,11 +44,9 @@ Usage:
$(call targetinfo)
-Gives a feedback, what build *stage* is just started. That's why it
-should always be the first call for each *stage*. For the package
-*foo* and the *compile stage* it will output:
-
-.. code-block:: bash
+Gives the user feedback about which build stage has just started.
+That's why it should always be the first call for each stage.
+For the package *foo* and the *compile* stage, this macro will output::
--------------------
target: foo.compile
@@ -63,11 +61,9 @@ Usage:
$(call touch)
-Gives a feedback, what build *stage* is just finished. That's why it
-should always be the last call for each *stage*. For the package
-*foo* and the *compile stage* it will output:
-
-.. code-block:: bash
+Gives the user feedback about which build stage has just finished.
+That's why it should always be the last call for each stage.
+For the package *foo* and the *compile* stage, this macro will output::
finished target foo.compile
@@ -123,7 +119,7 @@ Usage:
This macro is very similar to ``world/compile``. The only differences is
that is uses the specified ``build arguments`` instead of
-``<PKG>_MAKE_OPT``. This is usefull if ``make`` needs to be called more
+``<PKG>_MAKE_OPT``. This is useful if ``make`` needs to be called more
than once in the compile stage.
world/execute, execute
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-06-05 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:20 [ptxdist] [PATCH 1/2] doc: ref_make_macros: document the 'extract' macro Roland Hieber
2019-06-05 15:20 ` Roland Hieber [this message]
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=20190605152031.17474-2-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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