Fix broken links and header layout

agrest-docs-framework/src/docs/asciidoc/_chapters/_request-chains/strategies-for-object-matching.adoc

@@ -1,6 +1,6 @@
 === Strategies for Object Matching
 
-Many of the updating chains need to match objects coming as Update Documents (see link:/protocol#request-update-document[Request: Update Document]) against
+Many of the updating chains need to match objects coming as Update Documents (see link:/docs/4.x/protocol#update-document[Update Document]) against
 objects in the database. E.g. "createOrUpdate" needs to know whether a JSON object is new (and needs to be created)
 or it already exists (and needs to be updated). By default Agrest would attempt to match each JSON
 "id" attribute with a DB record primary key. This is a reasonable and useful strategy. Its

agrest-docs-framework/src/docs/asciidoc/_chapters/_writing-resource-endpoints/create-entity.adoc

@@ -18,7 +18,7 @@ public SimpleResponse create(String data) {
 Here we've built a very simple "create chain" using Agrest fluent API. It starts with a
 static "create" method on Agrest class, taking a type of entity to create (Domain) and
 previously injected Configuration. Finally it calls "sync" method to execute the
-request. "data" String is expected to be an "Update Document" (see link:/protocol#request-update-document[Request: Update Document]), i.e. a single object or an array of objects.
+request. "data" String is expected to be an "Update Document" (see link:/docs/4.x/protocol#update-document[Update Document]), i.e. a single object or an array of objects.
 Now if you compile your app and deploy it in a web container (e.g. Tomcat), you may call
 this endpoint to create new Domain objects:
 

agrest-docs-framework/src/docs/asciidoc/_chapters/_writing-resource-endpoints/read-collection-of-entities.adoc

@@ -37,7 +37,7 @@ Content-Type: application/json
 ----
 
 Since select chain above incorporates UriInfo, it will recognize Agrest control
-parameters passed from the client (see link:/protocol#control-parameters[Control Parameters]). Let's try using "exp" filter and "include":
+parameters passed from the client (see link:/docs/4.x/protocol#control-parameters[Control Parameters]). Let's try using "exp" filter and "include":
 
 
 `curl -i -X GET 'http://example.org/myapp/domain?exp=vhost="mysite1.example.org"&include=id'`

agrest-docs-protocol/src/docs/asciidoc/protocol.adoc

@@ -1,9 +1,9 @@
 :agrest-header: _chapters/header.html
 
-_Protocol Version 1.1_
-
 = Agrest Protocol
 
+_Protocol Version 1.1_
+
 include::_chapters/overview.adoc[]
 
 include::_chapters/json-documents.adoc[]