diff options
6 files changed, 14 insertions, 13 deletions
diff --git a/config-model/src/main/java/com/yahoo/vespa/model/package-info.java b/config-model/src/main/java/com/yahoo/vespa/model/package-info.java index 48a19037569..be1506c9418 100644 --- a/config-model/src/main/java/com/yahoo/vespa/model/package-info.java +++ b/config-model/src/main/java/com/yahoo/vespa/model/package-info.java @@ -36,7 +36,7 @@ com.yahoo.config.model.producer.AbstractConfigProducer allocation</a>. </p> - <h3>Config Generation</h3> + <h2>Config Generation</h2> <p>The method {@link com.yahoo.vespa.model.VespaModel#getConfig(com.yahoo.config.ConfigInstance.Builder, String) @@ -61,7 +61,7 @@ com.yahoo.config.model.producer.AbstractConfigProducer method and by user defined config. </p> - <h4>Example:</h4> + <h3>Example:</h3> <p> Say we have a config named 'sample' with an integer parameter named 'v'. If the VespaModel root node's {@link @@ -99,7 +99,7 @@ com.yahoo.config.model.producer.AbstractConfigProducer </p> - <h3 id="plugin_loading">Plugin Loading</h3> + <h2 id="plugin_loading">Plugin Loading</h2> <p>Each highest-level node in the setup file from the user's application specification corresponds to a {@link @@ -116,7 +116,7 @@ com.yahoo.config.model.builder.xml.ConfigModelBuilder ConfigModelBuilder}. The <p>The built models are given to other models that depends on it. </p> - <h4>Important notes for plugin developers:</h4> + <h3>Important notes for plugin developers:</h3> <ul> <li>The constructors of all child classes of {@link @@ -138,7 +138,7 @@ com.yahoo.config.model.producer.AbstractConfigProducer </ul> - <h3 id="port_allocation">Port Allocation</h3> + <h2 id="port_allocation">Port Allocation</h2> <p>Each {@link com.yahoo.vespa.model.Host Host} has an available dynamic port range running from {@link diff --git a/config-proxy/src/main/java/com/yahoo/vespa/config/proxy/package-info.java b/config-proxy/src/main/java/com/yahoo/vespa/config/proxy/package-info.java index 10e945ae202..b4c38c84482 100644 --- a/config-proxy/src/main/java/com/yahoo/vespa/config/proxy/package-info.java +++ b/config-proxy/src/main/java/com/yahoo/vespa/config/proxy/package-info.java @@ -14,7 +14,7 @@ the config client library. </p> - <h3>Why Vespa needs a config proxy</h3> + <h2>Why Vespa needs a config proxy</h2> <p>It is possible for a client to subscribe to config from the config server directly. However, if all Vespa diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java index a633e4bb291..950b3569319 100644 --- a/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java +++ b/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java @@ -3,7 +3,8 @@ * <p>Provides classes and interfaces for implementing an {@link com.yahoo.jdisc.application.Application * Application}.</p> * - * <h3>Application</h3> + * <h2>Application</h2> + * * <p>In every jDISC process there is exactly one Application instance, it is created during jDISC startup, and it is * destroyed during jDISC shutdown. The Application uses the {@link com.yahoo.jdisc.application.ContainerBuilder * ContainerBuilder} interface to load OSGi {@link org.osgi.framework.Bundle Bundles}, install Guice {@link @@ -52,7 +53,7 @@ void reconfigureApplication() { } </pre> * - * <h3>Application and OSGi</h3> + * <h2>Application and OSGi</h2> * <p>At the heart of jDISC is an OSGi framework. An Application is always packaged as an OSGi bundle. The OSGi * technology itself is a set of specifications that define a dynamic component system for Java. These specifications * enable a development model where applications are (dynamically) composed of many different (reusable) components. The @@ -105,7 +106,7 @@ void reconfigureApplication() { * into the application itself. Unless incompatible API changes are made to 3rd party jDISC components, it should be * possible to upgrade dependencies without having to recompile and redeploy the Application.</p> * - * <h3>Application deployment</h3> + * <h2>Application deployment</h2> * <p>jDISC allows a single binary to execute any application without having to change the command line parameters. * Instead of * modifying the parameters of the single application binary, changing the application is achieved by setting a single diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java index 1b08ef5e60c..088c9d5592d 100644 --- a/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java +++ b/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java @@ -3,7 +3,7 @@ * <p>Provides classes and interfaces for implementing a {@link com.yahoo.jdisc.handler.RequestHandler * RequestHandler}.</p> * - * <h3>RequestHandler</h3> + * <h2>RequestHandler</h2> * <p>All {@link com.yahoo.jdisc.Request Requests} in a jDISC application are processed by RequestHandlers. These are * components created by the {@link com.yahoo.jdisc.application.Application Application}, and bound to one or more URI * patterns through the {@link com.yahoo.jdisc.application.ContainerBuilder ContainerBuilder} API. Upon receiving a @@ -39,7 +39,7 @@ MyApplication(ContainerActivator activator, CurrentContainer container) { * otherwise, a jDISC application that is intended to forward large streams of data can do so without having to make any * copies of that data as it is passing through.</p> * - * <h3>ResponseHandler</h3> + * <h2>ResponseHandler</h2> * <p>The complement of the Request is the Response. A Response is a numeric status code and a set of header fields. * Just as Requests are processed by RequestHandlers, Responses are processed by ResponseHandlers. The ResponseHandler * interface is fully asynchronous, and uses the ContentChannel class to encapsulate the asynchronous passing of diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java index 532d2921469..cc2cd4abbef 100644 --- a/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java +++ b/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java @@ -3,7 +3,7 @@ * <p>Provides classes and interfaces for implementing a {@link com.yahoo.jdisc.service.ClientProvider ClientProvider} or * a {@link com.yahoo.jdisc.service.ServerProvider ServerProvider}.</p> * - * <h3>ServerProvider</h3> + * <h2>ServerProvider</h2> * <p>All {@link com.yahoo.jdisc.Request Requests} that are processed in a jDISC application are created by * ServerProviders. These are components created by the {@link com.yahoo.jdisc.application.Application Application}, and * they are the parts of jDISC that accept incoming connections. The ServerProvider creates and dispatches Request diff --git a/searchlib/src/main/java/com/yahoo/searchlib/rankingexpression/RankingExpression.java b/searchlib/src/main/java/com/yahoo/searchlib/rankingexpression/RankingExpression.java index 78d09b27b54..5a73d89cf2c 100755 --- a/searchlib/src/main/java/com/yahoo/searchlib/rankingexpression/RankingExpression.java +++ b/searchlib/src/main/java/com/yahoo/searchlib/rankingexpression/RankingExpression.java @@ -32,7 +32,7 @@ import java.util.Map; * <p>The identity of a ranking expression is decided by both its name and expression tree. Two expressions which * looks the same in string form are the same.</p> * - * <h3>Simple usage</h3> + * <h2>Simple usage</h2> <pre><code> try { MapContext context = new MapContext(); |