Fix minor doc issues #2081 #427 (#2119)

docs/se/config/04_property-mapping.adoc

@@ -181,6 +181,7 @@ If your application converts to the same
 target type in several places in the code, this approach allows you to change which mapper it uses by
 changing only the _registration_ of the mapper, not each use of it.
 
+[[WebConfig]]
 ==== Continuing the `Web` Example
 The following examples build on the example configuration from the
 <<config/01_introduction.adoc#create-simple-config-props,`application.properties`>>
@@ -287,6 +288,8 @@ uses reflection to invoke the methods and to map configuration values to fields/
 If you can change the target class you can add any one of the following methods or
 constructors to the POJO class which the config system will find and use for mapping.
 
+Continuing with the <<WebConfig,WebConfig>> example introduced earlier:
+
 .Methods Supporting Auto-mapping
 |===
 

docs/se/webserver/06_static-content-support.adoc

@@ -33,7 +33,7 @@ You can combine dynamic handlers with `StaticContentSupport` objects: if no file
 [source,java]
 ----
 Routing.builder()
-       .register("/pictures", StaticContentSupport.create(Paths.get("/some/WEB/pics")) // <1>
+       .register("/pictures", StaticContentSupport.create(Paths.get("/some/WEB/pics"))) // <1>
        .register("/", StaticContentSupport.builder("/static-content") // <2>
                                    .welcomeFileName("index.html") // <3>
                                    .build());