From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
"Akira Yokosawa" <akiyks@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: address some text issues with css/theme support
Date: Sat, 11 Dec 2021 09:12:53 -0800 [thread overview]
Message-ID: <58cb0905-3725-1aa7-4a32-317fa96e89f8@infradead.org> (raw)
In-Reply-To: <b0b166025019f7cc4f122bd789c79ba28cc2d29d.1639212812.git.mchehab+huawei@kernel.org>
On 12/11/21 00:57, Mauro Carvalho Chehab wrote:
> Fix:
> - overriden ->overridden
> - some whitespace issues introduced at the css/theme
> Makefile help.
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> See [PATCH 0/2] at: https://lore.kernel.org/all/cover.1639212812.git.mchehab+huawei@kernel.org/
>
> Documentation/Makefile | 4 ++--
> Documentation/doc-guide/sphinx.rst | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index c9543b63dc6a..9f4bd42cef18 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -159,8 +159,8 @@ dochelp:
> @echo ' make SPHINX_CONF={conf-file} [target] use *additional* sphinx-build'
> @echo ' configuration. This is e.g. useful to build with nit-picking config.'
> @echo
> - @echo ' make DOCS_THEME={sphinx-theme} selects a different Sphinx theme.'
> + @echo ' make DOCS_THEME={sphinx-theme} selects a different Sphinx theme.'
> @echo
> - @echo ' make DOCS_CSS={a .css file} adds a DOCS_CSS override file for html/epub output.'
> + @echo ' make DOCS_CSS={a .css file} adds a DOCS_CSS override file for html/epub output.'
> @echo
> @echo ' Default location for the generated documents is Documentation/output'
> diff --git a/Documentation/doc-guide/sphinx.rst b/Documentation/doc-guide/sphinx.rst
> index 7fb6e6168bbb..673cbb769c08 100644
> --- a/Documentation/doc-guide/sphinx.rst
> +++ b/Documentation/doc-guide/sphinx.rst
> @@ -147,7 +147,7 @@ By default, the build will try to use the Read the Docs sphinx theme:
>
> If the theme is not available, it will fall-back to the classic one.
>
> -The Sphinx theme can be overriden by using the ``DOCS_THEME`` make variable.
> +The Sphinx theme can be overridden by using the ``DOCS_THEME`` make variable.
>
> To remove the generated documentation, run ``make cleandocs``.
>
>
--
~Randy
next prev parent reply other threads:[~2021-12-11 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 8:56 [PATCH 0/2] Fix some issues with DOCS_CSS and DOCS_THEME Mauro Carvalho Chehab
2021-12-11 8:56 ` [PATCH 1/2] docs: Makefile: use the right path for DOCS_CSS Mauro Carvalho Chehab
2021-12-11 17:12 ` Randy Dunlap
2021-12-11 8:57 ` [PATCH 2/2] docs: address some text issues with css/theme support Mauro Carvalho Chehab
2021-12-11 17:12 ` Randy Dunlap [this message]
2021-12-16 22:55 ` [PATCH 0/2] Fix some issues with DOCS_CSS and DOCS_THEME Jonathan Corbet
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=58cb0905-3725-1aa7-4a32-317fa96e89f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
/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
all inboxes | Powered by JetHome®