[juneau-website] branch asf-site updated: Javadocs.

[jamesbognar]

This is an automated email from the ASF dual-hosted git repository.

jamesbognar pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/juneau-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new a0bc518  Javadocs.
a0bc518 is described below

commit a0bc518c5e7f8e2a6380603d08427d2022b22111
Author: JamesBognar <jamesbog...@apache.org>
AuthorDate: Mon Dec 31 14:44:14 2018 -0500

    Javadocs.
---
 content/site/apidocs-8.0.1/overview-summary.html | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/site/apidocs-8.0.1/overview-summary.html 
b/content/site/apidocs-8.0.1/overview-summary.html
index 6ac55c5..23694d1 100644
--- a/content/site/apidocs-8.0.1/overview-summary.html
+++ b/content/site/apidocs-8.0.1/overview-summary.html
@@ -13030,7 +13030,7 @@
 <p>
    A configuration can contain zero or more imports anywhere in the file.
    However, for clarity, imports should normally be placed in the default 
section of the configuration file.
-   The resolved configuration is retrieved from the configuration store used 
on the child configuration.
+   The resolved configuration is retrieved from the configuration store used 
for the child configuration.
 </p>
 <p>
    Configuration imports can be nested arbitrarily deep.
@@ -13063,7 +13063,7 @@
    <ci>&lt;ParentConfig1&gt;</ci>
    
    <cs>[Foo]</cs>
-   <ck>bar</ck> = <cv>quux</cv>
+   <ck>bar</ck> = <cv>baz</cv>
 </p>
 <p class='bpcode w800'>
    <cc># ParentConfig1 contents</cc>
@@ -13075,11 +13075,11 @@
 <p class='bpcode w800'>
    <cc># ParentConfig2 contents</cc>
    <cs>[Foo]</cs>
-   <ck>bar</ck> = <cv>baz</cv>
+   <ck>bar</ck> = <cv>quux</cv>
 </p>
 <p class='bpcode w800'>
    Config c = ConfigBuilder.<jsm>create</jsm>(<js>"MyConfig"</js>).build();
-   String foo = c.getString(<js>"Foo/bar"</js>);  <jc>// == "quux"</jc>
+   String foo = c.getString(<js>"Foo/bar"</js>);  <jc>// == "baz"</jc>
 </p>
 
 <p>
@@ -13118,14 +13118,14 @@
          triggered[0] = events.isKeyModified(<js>"Foo"</js>, <js>"bar"</js>));
       }
    };
-   c.addListener(c);
+   c.addListener(l);
    
    <jc>// Dynamically add an import to ParentConfig in the default 
section.</jc>
    c.setImport(<js>""</js>, <js>"ParentConfig"</js>);
    c.commit();
    
    <jc>// The new import statement should have triggered a config changes for 
imported values.</jc>
-   <jsf>assertTrue</jsf>(triggered[0]);   
+   <jsm>assertTrue</jsm>(triggered[0]);   
 </p>
 <p>
    Dynamically removing an import has the same effect as removing keys and 
generates <jsf>REMOVE_ENTRY</jsf> events.