diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1f8dba4eb6..7e90eb8ef1 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2040,7 +2040,8 @@
- Because the OpenEmbedded build system uses "signatures",
+ Because the OpenEmbedded build system uses
+ "signatures",
which are unique to a given build, the build system
knows when to rebuild packages.
All the inputs into a given task are represented by a
@@ -2128,7 +2129,7 @@
- The OpenEmbedded build system does not maintain
+ The OpenEmbedded build system does not maintain
PR information as part of the
shared state (sstate) packages.
If you maintain an sstate feed, its expected that either
@@ -2136,7 +2137,10 @@
feed use a shared PR Service, or you do not run a PR
Service on any of your building systems.
Having some systems use a PR Service while others do
- not leads to obvious problems.
+ not leads to obvious problems.
+ For more information on shared state, see the
+ "Shared State Cache"
+ section in the Yocto Project Reference Manual.
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index a9c31c8b6e..3393e15933 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -194,6 +194,18 @@
install them if they are deemed to be valid.
+
+ The OpenEmbedded build system does not maintain
+ PR information
+ as part of the Shared State packages.
+ Consequently, considerations exist that affect maintaining shared
+ state feeds.
+ For information on how the OpenEmbedded works with packages and can
+ track incrementing PR information, see the
+ "Incrementing a Package Revision Number"
+ section.
+
+
The rest of this section goes into detail about the overall incremental build
architecture, the checksums (signatures), shared state, and some tips and tricks.