From c387f0c2543a9dd7f8eca069629ede4bb5ec5dba Mon Sep 17 00:00:00 2001 From: Quentin Schulz Date: Thu, 17 Sep 2020 01:58:59 +0200 Subject: sphinx: replace special quotes with single and double quotes (From yocto-docs rev: 0aeb7a94abcef3cb3850c753dd0a243f381e6675) Signed-off-by: Quentin Schulz Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- documentation/ref-manual/faq.rst | 2 +- documentation/ref-manual/faq.xml | 2 +- documentation/ref-manual/ref-images.rst | 4 ++-- documentation/ref-manual/ref-images.xml | 4 ++-- documentation/ref-manual/ref-terms.rst | 2 +- documentation/ref-manual/ref-terms.xml | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index 04066e9202..2d2aaad0a9 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst @@ -143,7 +143,7 @@ various proxy types and configuring proxy servers, see the ":yocto_wiki:`Working Behind a Network Proxy `" Wiki page. -**Q:** What’s the difference between target and target\ ``-native``? +**Q:** What's the difference between target and target\ ``-native``? **A:** The ``*-native`` targets are designed to run on the system being used for the build. These are usually tools that are needed to assist diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 98ae0a975b..2f8fcf3242 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -323,7 +323,7 @@ - What’s the difference between target and target-native? + What's the difference between target and target-native? diff --git a/documentation/ref-manual/ref-images.rst b/documentation/ref-manual/ref-images.rst index 47beda0c23..f0229c3bb7 100644 --- a/documentation/ref-manual/ref-images.rst +++ b/documentation/ref-manual/ref-images.rst @@ -6,7 +6,7 @@ Images The OpenEmbedded build system provides several example images to satisfy different needs. When you issue the ``bitbake`` command you provide a -“top-level” recipe that essentially begins the build for the type of +"top-level" recipe that essentially begins the build for the type of image you want. .. note:: @@ -85,7 +85,7 @@ Following is a list of supported recipes: - ``core-image-minimal-initramfs``: A ``core-image-minimal`` image that has the Minimal RAM-based Initial Root Filesystem (initramfs) as part - of the kernel, which allows the system to find the first “init” + of the kernel, which allows the system to find the first "init" program more efficiently. See the :term:`PACKAGE_INSTALL` variable for additional information helpful when working with initramfs images. diff --git a/documentation/ref-manual/ref-images.xml b/documentation/ref-manual/ref-images.xml index aaeda55226..6f10a6fd2a 100644 --- a/documentation/ref-manual/ref-images.xml +++ b/documentation/ref-manual/ref-images.xml @@ -9,7 +9,7 @@ The OpenEmbedded build system provides several example images to satisfy different needs. - When you issue the bitbake command you provide a “top-level” recipe + When you issue the bitbake command you provide a "top-level" recipe that essentially begins the build for the type of image you want. @@ -100,7 +100,7 @@ core-image-minimal-initramfs: A core-image-minimal image that has the Minimal RAM-based Initial Root Filesystem (initramfs) as part of the kernel, - which allows the system to find the first “init” program more efficiently. + which allows the system to find the first "init" program more efficiently. See the PACKAGE_INSTALL variable for additional information helpful when working with diff --git a/documentation/ref-manual/ref-terms.rst b/documentation/ref-manual/ref-terms.rst index 312fc12ef0..6e7e5169ce 100644 --- a/documentation/ref-manual/ref-terms.rst +++ b/documentation/ref-manual/ref-terms.rst @@ -273,7 +273,7 @@ universal, the list includes them just in case: Arbitrary groups of software Recipes. You use package groups to hold recipes that, when built, usually accomplish a single task. For example, a package group could contain the recipes - for a company’s proprietary or value-add software. Or, the package + for a company's proprietary or value-add software. Or, the package group could contain the recipes that enable graphics. A package group is really just another recipe. Because package group files are recipes, they end with the ``.bb`` filename extension. diff --git a/documentation/ref-manual/ref-terms.xml b/documentation/ref-manual/ref-terms.xml index d2605c62a8..2a0452bd78 100644 --- a/documentation/ref-manual/ref-terms.xml +++ b/documentation/ref-manual/ref-terms.xml @@ -365,7 +365,7 @@ You use package groups to hold recipes that, when built, usually accomplish a single task. For example, a package group could contain the recipes for a - company’s proprietary or value-add software. + company's proprietary or value-add software. Or, the package group could contain the recipes that enable graphics. A package group is really just another recipe. -- cgit v1.2.3-54-g00ecf