[05/27] isis-site git commit: ISIS-1291: moved internal framework services into its own guide

[da...@apache.org]

http://git-wip-us.apache.org/repos/asf/isis-site/blob/cb86cd1e/content/guides/ugvro.html
----------------------------------------------------------------------
diff --git a/content/guides/ugvro.html b/content/guides/ugvro.html
index 38c361d..d81466e 100644
--- a/content/guides/ugvro.html
+++ b/content/guides/ugvro.html
@@ -569,6 +569,9 @@ standard third-party configurations.</p>
 <li>
 <p><a href="rgmvn.html">Apache Isis Maven plugin</a></p>
 </li>
+<li>
+<p><a href="rgfis.html">Framework Internal Services</a></p>
+</li>
 </ul>
 </div>
 <div class="paragraph">
@@ -883,7 +886,7 @@ the <code>Content-Type</code> header which the client can use to know how to pro
 <li>
 <p><code>RepresentationService</code><br></p>
 <div class="paragraph">
-<p>The <a href="rgsvc.html#_rgsvc_spi_RepresentationService"><code>RepresentationService</code></a> is an SPI domain service (plugin-point)
+<p>The <a href="rgfis.html#_rgfis_spi_RepresentationService"><code>RepresentationService</code></a> is an SPI domain service (plugin-point)
 that allows an arbitrary representation to be generated for any of the resources defined in the RO spec.<br></p>
 </div>
 <div class="paragraph">
@@ -898,7 +901,7 @@ is able to handle the request (per the chain of responsibliity pattern).</p>
 <p><code>ContentNegotiationService</code><br></p>
 <div class="paragraph">
 <p>As noted above, there can be multiple implementations of the
-<a href="rgsvc.html#_rgsvc_spi_ContentNegotiationService"><code>ContentNegotiationService</code></a>, each one handling a particular
+<a href="rgfis.html#_rgfis_spi_ContentNegotiationService"><code>ContentNegotiationService</code></a>, each one handling a particular
 HTTP <code>Accept</code> header.  If the implementation does not recognize the value of the header, if can simply return <code>null</code>.<br></p>
 </div>
 <div class="paragraph">