summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-10-16 13:18:12 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-10-30 15:55:05 +0000
commite41c30aa33fdffe142c8c2e14ae0e76ac5f4f3cb (patch)
tree46306562a1324c9e8bf29e9ac763e98ec646ee85 /documentation
parent195d33516a09a71e05f695af215575465c088a39 (diff)
downloadpoky-e41c30aa33fdffe142c8c2e14ae0e76ac5f4f3cb.tar.gz
ref-manual: Changed dev-manual title and fixed links
Fixed a couple links that were still going to the dev-manual when they should have been going to the ref-manual. Updated the title to the dev-manual for those links. (From yocto-docs rev: 0cd84696a569af17a12bb939f203051e78d6fd48) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/introduction.xml13
1 files changed, 7 insertions, 6 deletions
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml
index 1fe1372898..1376d96c8a 100644
--- a/documentation/ref-manual/introduction.xml
+++ b/documentation/ref-manual/introduction.xml
@@ -33,7 +33,7 @@
33 without having to understand concepts, work through the 33 without having to understand concepts, work through the
34 <ulink url='&YOCTO_DOCS_QS_URL;'>Yocto Project Quick Start</ulink>. 34 <ulink url='&YOCTO_DOCS_QS_URL;'>Yocto Project Quick Start</ulink>.
35 You can find "how-to" information in the 35 You can find "how-to" information in the
36 <ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Manual</ulink>. 36 <ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Tasks Manual</ulink>.
37 <note><title>Tip</title> 37 <note><title>Tip</title>
38 For more information about the Yocto Project Documentation set, 38 For more information about the Yocto Project Documentation set,
39 see the 39 see the
@@ -154,7 +154,8 @@
154 <ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink> 154 <ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink>
155 and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>. 155 and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>.
156 See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>" 156 See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>"
157 section in the Yocto Project Development Manual for more information. 157 section in the Yocto Project Development Tasks Manual for more
158 information.
158 </para> 159 </para>
159</section> 160</section>
160 161
@@ -651,12 +652,12 @@
651 <title>Development Checkouts</title> 652 <title>Development Checkouts</title>
652 <para> 653 <para>
653 Development using the Yocto Project requires a local 654 Development using the Yocto Project requires a local
654 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 655 <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
655 You can set up the Source Directory by cloning a copy of the upstream 656 You can set up the Source Directory by cloning a copy of the upstream
656 <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> Git repository. 657 <ulink url='&YOCTO_DOCS_REF_URL;#poky'>poky</ulink> Git repository.
657 For information on how to do this, see the 658 For information on how to do this, see the
658 "<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-yocto-project-source-files'>Working With Yocto Project Source Files</ulink>" 659 "<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-yocto-project-source-files'>Working With Yocto Project Source Files</ulink>"
659 section in the Yocto Project Development Manual. 660 section in the Yocto Project Development Tasks Manual.
660 </para> 661 </para>
661</section> 662</section>
662 663
@@ -687,7 +688,7 @@
687 information in the similarly-named recipe file. 688 information in the similarly-named recipe file.
688 For an example of an append file in use, see the 689 For an example of an append file in use, see the
689 "<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer</ulink>" 690 "<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer</ulink>"
690 section in the Yocto Project Development Manual. 691 section in the Yocto Project Development Tasks Manual.
691 <note> 692 <note>
692 Append files can also use wildcard patterns in their 693 Append files can also use wildcard patterns in their
693 version numbers so they can be applied to more than one 694 version numbers so they can be applied to more than one