summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/README2
-rw-r--r--documentation/bsp-guide/bsp.rst4
-rw-r--r--documentation/dev-manual/common-tasks.rst8
-rw-r--r--documentation/kernel-dev/common.rst2
-rw-r--r--documentation/kernel-dev/maint-appx.rst2
-rw-r--r--documentation/overview-manual/yp-intro.rst16
-rw-r--r--documentation/profile-manual/usage.rst4
-rw-r--r--documentation/ref-manual/TODO6
-rw-r--r--documentation/ref-manual/classes.rst2
-rw-r--r--documentation/ref-manual/faq.rst2
-rw-r--r--documentation/ref-manual/migration-1.7.rst2
-rw-r--r--documentation/ref-manual/release-process.rst2
-rw-r--r--documentation/ref-manual/system-requirements.rst2
-rw-r--r--documentation/ref-manual/variables.rst4
-rw-r--r--documentation/sdk-manual/appendix-customizing.rst2
-rw-r--r--documentation/test-manual/understand-autobuilder.rst4
-rw-r--r--documentation/toaster-manual/reference.rst2
17 files changed, 33 insertions, 33 deletions
diff --git a/documentation/README b/documentation/README
index 159ec94608..b491e46a1d 100644
--- a/documentation/README
+++ b/documentation/README
@@ -109,7 +109,7 @@ obvious reasons, we will only support building the Yocto Project
109documentation with Python3. 109documentation with Python3.
110 110
111Sphinx might be available in your Linux distro packages repositories, 111Sphinx might be available in your Linux distro packages repositories,
112however it is not recommend to use distro packages, as they might be 112however it is not recommended to use distro packages, as they might be
113old versions, especially if you are using an LTS version of your 113old versions, especially if you are using an LTS version of your
114distro. The recommended method to install Sphinx and all required 114distro. The recommended method to install Sphinx and all required
115dependencies is to use the Python Package Index (pip). 115dependencies is to use the Python Package Index (pip).
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
index c24ab28ea2..89f1564422 100644
--- a/documentation/bsp-guide/bsp.rst
+++ b/documentation/bsp-guide/bsp.rst
@@ -250,7 +250,7 @@ standardization of software support for hardware.
250The proposed form described in this section does have elements that are 250The proposed form described in this section does have elements that are
251specific to the OpenEmbedded build system. It is intended that 251specific to the OpenEmbedded build system. It is intended that
252developers can use this structure with other build systems besides the 252developers can use this structure with other build systems besides the
253OpenEmbedded build system. It is also intended that it will be be simple 253OpenEmbedded build system. It is also intended that it will be simple
254to extract information and convert it to other formats if required. The 254to extract information and convert it to other formats if required. The
255OpenEmbedded build system, through its standard :ref:`layers mechanism 255OpenEmbedded build system, through its standard :ref:`layers mechanism
256<overview-manual/yp-intro:the yocto project layer model>`, can 256<overview-manual/yp-intro:the yocto project layer model>`, can
@@ -1036,7 +1036,7 @@ the following:
1036 to reside in a machine-specific directory. 1036 to reside in a machine-specific directory.
1037 1037
1038Following is a specific example to help you better understand the 1038Following is a specific example to help you better understand the
1039process. This example customizes customizes a recipe by adding a 1039process. This example customizes a recipe by adding a
1040BSP-specific configuration file named ``interfaces`` to the 1040BSP-specific configuration file named ``interfaces`` to the
1041``init-ifupdown_1.0.bb`` recipe for machine "xyz" where the BSP layer 1041``init-ifupdown_1.0.bb`` recipe for machine "xyz" where the BSP layer
1042also supports several other machines: 1042also supports several other machines:
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index faa5efeb52..e5a90e15df 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -2065,7 +2065,7 @@ A subset of the files installed by the
2065:ref:`ref-tasks-install` task are 2065:ref:`ref-tasks-install` task are
2066used by the 2066used by the
2067:ref:`ref-tasks-populate_sysroot` 2067:ref:`ref-tasks-populate_sysroot`
2068task as defined by the the 2068task as defined by the
2069:term:`SYSROOT_DIRS` variable to 2069:term:`SYSROOT_DIRS` variable to
2070automatically populate the sysroot. It is possible to modify the list of 2070automatically populate the sysroot. It is possible to modify the list of
2071directories that populate the sysroot. The following example shows how 2071directories that populate the sysroot. The following example shows how
@@ -4591,7 +4591,7 @@ directory:
4591 section. 4591 section.
4592 4592
4593 3. Once you have the correct source revisions, you can modify 4593 3. Once you have the correct source revisions, you can modify
4594 those recipes to to set ``SRCREV`` to specific versions of the 4594 those recipes to set ``SRCREV`` to specific versions of the
4595 software. 4595 software.
4596 4596
4597Speeding Up a Build 4597Speeding Up a Build
@@ -6599,7 +6599,7 @@ Quality <#maintaining-build-output-quality>`__" section.
6599 6599
6600 The OpenEmbedded build system does not maintain ``PR`` information as 6600 The OpenEmbedded build system does not maintain ``PR`` information as
6601 part of the shared state (sstate) packages. If you maintain an sstate 6601 part of the shared state (sstate) packages. If you maintain an sstate
6602 feed, its expected that either all your building systems that 6602 feed, it's expected that either all your building systems that
6603 contribute to the sstate feed use a shared PR Service, or you do not 6603 contribute to the sstate feed use a shared PR Service, or you do not
6604 run a PR Service on any of your building systems. Having some systems 6604 run a PR Service on any of your building systems. Having some systems
6605 use a PR Service while others do not leads to obvious problems. 6605 use a PR Service while others do not leads to obvious problems.
@@ -7070,7 +7070,7 @@ runtime package management of RPM packages. In order to use DNF for
7070runtime package management, you must perform an initial setup on the 7070runtime package management, you must perform an initial setup on the
7071target machine for cases where the ``PACKAGE_FEED_*`` variables were not 7071target machine for cases where the ``PACKAGE_FEED_*`` variables were not
7072set as part of the image that is running on the target. This means if 7072set as part of the image that is running on the target. This means if
7073you built your image and did not not use these variables as part of the 7073you built your image and did not use these variables as part of the
7074build and your image is now running on the target, you need to perform 7074build and your image is now running on the target, you need to perform
7075the steps in this section if you want to use runtime package management. 7075the steps in this section if you want to use runtime package management.
7076 7076
diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst
index 0e545d1b89..3878f831be 100644
--- a/documentation/kernel-dev/common.rst
+++ b/documentation/kernel-dev/common.rst
@@ -1914,7 +1914,7 @@ differences:
1914 $ git show origin/standard/base..origin/standard/emenlow 1914 $ git show origin/standard/base..origin/standard/emenlow
1915 1915
1916Use this command to create individual patches for each change. Here is 1916Use this command to create individual patches for each change. Here is
1917an example that that creates patch files for each commit and places them 1917an example that creates patch files for each commit and places them
1918in your ``Documents`` directory: 1918in your ``Documents`` directory:
1919:: 1919::
1920 1920
diff --git a/documentation/kernel-dev/maint-appx.rst b/documentation/kernel-dev/maint-appx.rst
index 89f4b43343..44c43893e2 100644
--- a/documentation/kernel-dev/maint-appx.rst
+++ b/documentation/kernel-dev/maint-appx.rst
@@ -64,7 +64,7 @@ the "yocto-4.12" branch of the ``yocto-kernel-cache`` repository:
64 kernel versions (e.g. "yocto-4.12", "yocto-4.10", "yocto-4.9", and so forth). 64 kernel versions (e.g. "yocto-4.12", "yocto-4.10", "yocto-4.9", and so forth).
65 65
66Once you have checked out and switched to appropriate branches, you can 66Once you have checked out and switched to appropriate branches, you can
67see a snapshot of all the kernel source files used to used to build that 67see a snapshot of all the kernel source files used to build that
68particular Yocto Linux kernel for a particular board. 68particular Yocto Linux kernel for a particular board.
69 69
70To see the features and configurations for a particular Yocto Linux 70To see the features and configurations for a particular Yocto Linux
diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
index 0ec7e2b961..176e5b24c3 100644
--- a/documentation/overview-manual/yp-intro.rst
+++ b/documentation/overview-manual/yp-intro.rst
@@ -272,7 +272,7 @@ of the ``poky`` repository, you will see several layers: ``meta``,
272``meta-yocto-bsp``. Each of these repositories represents a distinct 272``meta-yocto-bsp``. Each of these repositories represents a distinct
273layer. 273layer.
274 274
275For procedures on how to create layers, see the 275For procedures on how to create layers, see the
276":ref:`dev-manual/common-tasks:understanding and creating layers`" 276":ref:`dev-manual/common-tasks:understanding and creating layers`"
277section in the Yocto Project Development Tasks Manual. 277section in the Yocto Project Development Tasks Manual.
278 278
@@ -283,7 +283,7 @@ The Yocto Project employs a collection of components and tools used by
283the project itself, by project developers, and by those using the Yocto 283the project itself, by project developers, and by those using the Yocto
284Project. These components and tools are open source projects and 284Project. These components and tools are open source projects and
285metadata that are separate from the reference distribution 285metadata that are separate from the reference distribution
286(:term:`Poky`) and the 286(:term:`Poky`) and the
287:term:`OpenEmbedded Build System`. Most of the 287:term:`OpenEmbedded Build System`. Most of the
288components and tools are downloaded separately. 288components and tools are downloaded separately.
289 289
@@ -325,7 +325,7 @@ applications using the Yocto Project:
325 325
326 You can read about the ``devtool`` workflow in the Yocto Project 326 You can read about the ``devtool`` workflow in the Yocto Project
327 Application Development and Extensible Software Development Kit 327 Application Development and Extensible Software Development Kit
328 (eSDK) Manual in the 328 (eSDK) Manual in the
329 ":ref:`sdk-manual/extensible:using \`\`devtool\`\` in your sdk workflow`" 329 ":ref:`sdk-manual/extensible:using \`\`devtool\`\` in your sdk workflow`"
330 section. 330 section.
331 331
@@ -571,7 +571,7 @@ Linux.
571Development Methods 571Development Methods
572=================== 572===================
573 573
574The Yocto Project development environment usually involves a 574The Yocto Project development environment usually involves a
575:term:`Build Host` and target 575:term:`Build Host` and target
576hardware. You use the Build Host to build images and develop 576hardware. You use the Build Host to build images and develop
577applications, while you use the target hardware to test deployed 577applications, while you use the target hardware to test deployed
@@ -597,7 +597,7 @@ Project.
597 supported Linux distribution. 597 supported Linux distribution.
598 598
599 For information on how to set up a Build Host on a system running 599 For information on how to set up a Build Host on a system running
600 Linux as its native operating system, see the 600 Linux as its native operating system, see the
601 ":ref:`dev-manual/start:setting up a native linux host`" 601 ":ref:`dev-manual/start:setting up a native linux host`"
602 section in the Yocto Project Development Tasks Manual. 602 section in the Yocto Project Development Tasks Manual.
603 603
@@ -646,7 +646,7 @@ Project.
646 builds is collected and stored in a database. You can use Toaster to 646 builds is collected and stored in a database. You can use Toaster to
647 configure and start builds on multiple remote build servers. 647 configure and start builds on multiple remote build servers.
648 648
649 For information about and how to use Toaster, see the 649 For information about and how to use Toaster, see the
650 :doc:`/toaster-manual/index`. 650 :doc:`/toaster-manual/index`.
651 651
652Reference Embedded Distribution (Poky) 652Reference Embedded Distribution (Poky)
@@ -820,10 +820,10 @@ helpful for getting started:
820 them. You can search the Layer Index for layers used within Yocto 820 them. You can search the Layer Index for layers used within Yocto
821 Project. 821 Project.
822 822
823 For more detailed information on layers, see the 823 For more detailed information on layers, see the
824 ":ref:`dev-manual/common-tasks:understanding and creating layers`" 824 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
825 section in the Yocto Project Development Tasks Manual. For a 825 section in the Yocto Project Development Tasks Manual. For a
826 discussion specifically on BSP Layers, see the 826 discussion specifically on BSP Layers, see the
827 ":ref:`bsp-guide/bsp:bsp layers`" section in the Yocto 827 ":ref:`bsp-guide/bsp:bsp layers`" section in the Yocto
828 Project Board Support Packages (BSP) Developer's Guide. 828 Project Board Support Packages (BSP) Developer's Guide.
829 829
diff --git a/documentation/profile-manual/usage.rst b/documentation/profile-manual/usage.rst
index fd6da6fc41..c42f5b64b2 100644
--- a/documentation/profile-manual/usage.rst
+++ b/documentation/profile-manual/usage.rst
@@ -256,7 +256,7 @@ important for now), which takes the buffers the kernel passes to it and
256writes it to a disk file to save it. 256writes it to a disk file to save it.
257 257
258The part of this process that we're looking at in the above call stacks 258The part of this process that we're looking at in the above call stacks
259is the part where the kernel passes the data it's read from the socket 259is the part where the kernel passes the data it has read from the socket
260down to wget i.e. a copy-to-user. 260down to wget i.e. a copy-to-user.
261 261
262Notice also that here there's also a case where the hex value is 262Notice also that here there's also a case where the hex value is
@@ -1580,7 +1580,7 @@ events in the output buffer: ::
1580 root@sugarbay:/sys/kernel/debug/tracing# echo nop > current_tracer 1580 root@sugarbay:/sys/kernel/debug/tracing# echo nop > current_tracer
1581 root@sugarbay:/sys/kernel/debug/tracing# echo 1 > tracing_on 1581 root@sugarbay:/sys/kernel/debug/tracing# echo 1 > tracing_on
1582 1582
1583Now, if we look at the the 'trace' file, we see nothing 1583Now, if we look at the 'trace' file, we see nothing
1584but the kmalloc events we just turned on: :: 1584but the kmalloc events we just turned on: ::
1585 1585
1586 root@sugarbay:/sys/kernel/debug/tracing# cat trace | less 1586 root@sugarbay:/sys/kernel/debug/tracing# cat trace | less
diff --git a/documentation/ref-manual/TODO b/documentation/ref-manual/TODO
index ee0db977cc..0510f54710 100644
--- a/documentation/ref-manual/TODO
+++ b/documentation/ref-manual/TODO
@@ -1,10 +1,10 @@
1Handbook Todo List: 1Handbook Todo List:
2 2
3 * Document adding a new IMAGE_FEATURE to the customising images section 3 * Document adding a new IMAGE_FEATURE to the customising images section
4 * Add instructions about using zaurus/openmoko emulation 4 * Add instructions about using zaurus/openmoko emulation
5 * Add component overview/block diagrams 5 * Add component overview/block diagrams
6 * Software Deevelopment intro should mention its software development for 6 * Software Development intro should mention its software development for
7 intended target and could be a different arch etc and thus special case. 7 intended target and could be a different arch etc and thus special case.
8 * Expand insane.bbclass documentation to cover tests 8 * Expand insane.bbclass documentation to cover tests
9 * Document remaining classes (see list in ref-classes) 9 * Document remaining classes (see list in ref-classes)
10 * Document formfactor 10 * Document formfactor
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index be112e0faf..6d9779f6e7 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -1426,7 +1426,7 @@ Only a single U-boot boot script can be added to the FIT image created by
1426The boot script is specified in the ITS file as a text file containing 1426The boot script is specified in the ITS file as a text file containing
1427U-boot commands. When using a boot script the user should configure the 1427U-boot commands. When using a boot script the user should configure the
1428U-boot ``do_install`` task to copy the script to sysroot. 1428U-boot ``do_install`` task to copy the script to sysroot.
1429So the script can be included in the the FIT image by the ``kernel-fitimage`` 1429So the script can be included in the FIT image by the ``kernel-fitimage``
1430class. At run-time, U-boot CONFIG_BOOTCOMMAND define can be configured to 1430class. At run-time, U-boot CONFIG_BOOTCOMMAND define can be configured to
1431load the boot script from the FIT image and executes it. 1431load the boot script from the FIT image and executes it.
1432 1432
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
index 34b26ee3ef..3b65588caa 100644
--- a/documentation/ref-manual/faq.rst
+++ b/documentation/ref-manual/faq.rst
@@ -449,7 +449,7 @@ variable ``bindir``. The makefile's hardcoded default value of
449"/usr/bin" worked most of the time, but not for the recipe's ``-native`` 449"/usr/bin" worked most of the time, but not for the recipe's ``-native``
450variant. For another example, permissions errors might be caused by a 450variant. For another example, permissions errors might be caused by a
451Makefile that ignores ``DESTDIR`` or uses a different name for that 451Makefile that ignores ``DESTDIR`` or uses a different name for that
452environment variable. Check the the build system to see if these kinds 452environment variable. Check the build system to see if these kinds
453of issues exist. 453of issues exist.
454 454
455**Q:** I'm adding a binary in a recipe but it's different in the image, what is 455**Q:** I'm adding a binary in a recipe but it's different in the image, what is
diff --git a/documentation/ref-manual/migration-1.7.rst b/documentation/ref-manual/migration-1.7.rst
index 54544e4798..c00768ca7b 100644
--- a/documentation/ref-manual/migration-1.7.rst
+++ b/documentation/ref-manual/migration-1.7.rst
@@ -12,7 +12,7 @@ Changes to Setting QEMU ``PACKAGECONFIG`` Options in ``local.conf``
12The QEMU recipe now uses a number of 12The QEMU recipe now uses a number of
13:term:`PACKAGECONFIG` options to enable various 13:term:`PACKAGECONFIG` options to enable various
14optional features. The method used to set defaults for these options 14optional features. The method used to set defaults for these options
15means that existing ``local.conf`` files will need to be be modified to 15means that existing ``local.conf`` files will need to be modified to
16append to ``PACKAGECONFIG`` for ``qemu-native`` and ``nativesdk-qemu`` 16append to ``PACKAGECONFIG`` for ``qemu-native`` and ``nativesdk-qemu``
17instead of setting it. In other words, to enable graphical output for 17instead of setting it. In other words, to enable graphical output for
18QEMU, you should now have these lines in ``local.conf``: 18QEMU, you should now have these lines in ``local.conf``:
diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst
index ed5a09a55d..107d06c76d 100644
--- a/documentation/ref-manual/release-process.rst
+++ b/documentation/ref-manual/release-process.rst
@@ -135,7 +135,7 @@ consists of the following pieces:
135 135
136- :ref:`ptest <dev-manual/common-tasks:testing packages with ptest>`: 136- :ref:`ptest <dev-manual/common-tasks:testing packages with ptest>`:
137 Runs tests against packages produced during the build for a given 137 Runs tests against packages produced during the build for a given
138 piece of software. The test allows the packages to be be run within a 138 piece of software. The test allows the packages to be run within a
139 target image. 139 target image.
140 140
141- ``oe-selftest``: Tests combination BitBake invocations. These tests 141- ``oe-selftest``: Tests combination BitBake invocations. These tests
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
index 9f423e7bb5..6edfa1a865 100644
--- a/documentation/ref-manual/system-requirements.rst
+++ b/documentation/ref-manual/system-requirements.rst
@@ -294,7 +294,7 @@ installer and automatically installs the tools for you:
294 294
295 During execution, the buildtools tarball will be downloaded, the 295 During execution, the buildtools tarball will be downloaded, the
296 checksum of the download will be verified, the installer will be run 296 checksum of the download will be verified, the installer will be run
297 for you, and some basic checks will be run to to make sure the 297 for you, and some basic checks will be run to make sure the
298 installation is functional. 298 installation is functional.
299 299
300 To avoid the need of ``sudo`` privileges, the ``install-buildtools`` 300 To avoid the need of ``sudo`` privileges, the ``install-buildtools``
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index f551c4d376..6a9fed0c68 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -2991,7 +2991,7 @@ system and gives an overview of their function and contents.
2991 2991
2992 :term:`IMAGE_CMD` 2992 :term:`IMAGE_CMD`
2993 Specifies the command to create the image file for a specific image 2993 Specifies the command to create the image file for a specific image
2994 type, which corresponds to the value set set in 2994 type, which corresponds to the value set in
2995 :term:`IMAGE_FSTYPES`, (e.g. ``ext3``, 2995 :term:`IMAGE_FSTYPES`, (e.g. ``ext3``,
2996 ``btrfs``, and so forth). When setting this variable, you should use 2996 ``btrfs``, and so forth). When setting this variable, you should use
2997 an override for the associated type. Here is an example: 2997 an override for the associated type. Here is an example:
@@ -3458,7 +3458,7 @@ system and gives an overview of their function and contents.
3458 3458
3459 This will result in ``INCOMPATIBLE_LICENSE`` containing the names of 3459 This will result in ``INCOMPATIBLE_LICENSE`` containing the names of
3460 all licenses from :term:`AVAILABLE_LICENSES` except the ones specified 3460 all licenses from :term:`AVAILABLE_LICENSES` except the ones specified
3461 in ``COMPATIBLE_LICENSES`` , thus only allowing the latter licenses to 3461 in ``COMPATIBLE_LICENSES``, thus only allowing the latter licenses to
3462 be used. 3462 be used.
3463 3463
3464 :term:`INHERIT` 3464 :term:`INHERIT`
diff --git a/documentation/sdk-manual/appendix-customizing.rst b/documentation/sdk-manual/appendix-customizing.rst
index 97ade0801d..cdfde8b4b2 100644
--- a/documentation/sdk-manual/appendix-customizing.rst
+++ b/documentation/sdk-manual/appendix-customizing.rst
@@ -139,7 +139,7 @@ Changing the Extensible SDK Installer Title
139 139
140You can change the displayed title for the SDK installer by setting the 140You can change the displayed title for the SDK installer by setting the
141:term:`SDK_TITLE` variable and then 141:term:`SDK_TITLE` variable and then
142rebuilding the the SDK installer. For information on how to build an SDK 142rebuilding the SDK installer. For information on how to build an SDK
143installer, see the "`Building an SDK 143installer, see the "`Building an SDK
144Installer <#sdk-building-an-sdk-installer>`__" section. 144Installer <#sdk-building-an-sdk-installer>`__" section.
145 145
diff --git a/documentation/test-manual/understand-autobuilder.rst b/documentation/test-manual/understand-autobuilder.rst
index 2d9d6735a9..c158d9ce4d 100644
--- a/documentation/test-manual/understand-autobuilder.rst
+++ b/documentation/test-manual/understand-autobuilder.rst
@@ -111,7 +111,7 @@ roughly consist of:
111 :ref:`test-manual/understand-autobuilder:Autobuilder Clone Cache`. 111 :ref:`test-manual/understand-autobuilder:Autobuilder Clone Cache`.
112 112
113 This step has two possible modes of operation. If the build is part 113 This step has two possible modes of operation. If the build is part
114 of a parent build, its possible that all the repositories needed may 114 of a parent build, it's possible that all the repositories needed may
115 already be available, ready in a pre-prepared directory. An "a-quick" 115 already be available, ready in a pre-prepared directory. An "a-quick"
116 or "a-full" build would prepare this before starting the other 116 or "a-full" build would prepare this before starting the other
117 sub-target builds. This is done for two reasons: 117 sub-target builds. This is done for two reasons:
@@ -130,7 +130,7 @@ roughly consist of:
130 130
131#. *Call scripts/run-config* 131#. *Call scripts/run-config*
132 132
133 This is another call into the Helper scripts where its expected that 133 This is another call into the Helper scripts where it's expected that
134 the main functionality of this target will be executed. 134 the main functionality of this target will be executed.
135 135
136Autobuilder Technology 136Autobuilder Technology
diff --git a/documentation/toaster-manual/reference.rst b/documentation/toaster-manual/reference.rst
index 8ef58182e7..3d4efe92d6 100644
--- a/documentation/toaster-manual/reference.rst
+++ b/documentation/toaster-manual/reference.rst
@@ -208,7 +208,7 @@ Customizing Pre-Set Data
208------------------------ 208------------------------
209 209
210The pre-set data for Toaster is easily customizable. You can create the 210The pre-set data for Toaster is easily customizable. You can create the
211``orm/fixtures/custom.xml`` file to customize the values that go into to 211``orm/fixtures/custom.xml`` file to customize the values that go into
212the database. Customization is additive, and can either extend or 212the database. Customization is additive, and can either extend or
213completely replace the existing values. 213completely replace the existing values.
214 214