summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml2
-rw-r--r--documentation/dev-manual/dev-manual-kernel-appendix.xml2
-rw-r--r--documentation/dev-manual/dev-manual-model.xml27
3 files changed, 6 insertions, 25 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index 3c0ab28..44ffe31 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -3,7 +3,7 @@
<appendix id='dev-manual-bsp-appendix'>
-<title>BSP Development Case</title>
+<title>BSP Development Example</title>
<para>
This appendix provides a complete BSP example.
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index 608fc32..c5fd3e3 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -3,7 +3,7 @@
<appendix id='dev-manual-kernel-appendix'>
-<title>Kernel Modification Case</title>
+<title>Kernel Modification Example</title>
<para>
Kernel modification involves changing or adding configurations to an existing kernel, or
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 6b60b4c..b07fe50 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -6,20 +6,6 @@
<title>Common Development Models</title>
<para>
- [WRITERS NOTE: This chapter presents common development models within the Yocto Project.
- Reading this chapter will give the user a feel for the overall development process.
- The chapter will follow the framework for the manual.
- The team decided to present a single development model and not to try and represent all the
- various possibilities that might exist.
- The chapter will include an over-arching diagram that shows a simple, most-common development model.
- The diagram will consist of boxes that represent high-level areas of the development process.
- For example, a box for “Setting Up” will be in the model.
- A box for “Debugging” will exist.
- The diagram needs to account for the two use-cases we are going to showcase
- (system development and application development)].
-</para>
-
-<para>
Many development models exist for which you can use the Yocto Project.
However, for the purposes of this manual we are going to focus on two common ones:
System Development and User Application Development.
@@ -29,15 +15,10 @@
</para>
<para>
- This chapter presents an overview of the primary models.
- Supsequent appendices in the manual provide detailed explanations of the examples.
-</para>
-
-<para>
- [WRITERS NOTE: What is undetermined at this point is how much of the entire development process
- we include in this particular chapter.
- In other words, do we cover debugging and emulation steps here on a case-specific basis?
- Or, do we capture that information in the appropriate subsequent chapter by case?]
+ This chapter presents overviews of both system and application models.
+ If you want to reference specific examples of these development models,
+ see <xref linkend='dev-manual-bsp-appendix'>BSP Development Example</xref> and
+ <xref linkend='dev-manual-kernel-appendix'>Kernel Modification Example</xref>.
</para>
<section id='system-development-model'>
OpenPOWER on IntegriCloud