WELD-2431 Update development tool docs

- remove the link to OpenShift demo
- use Weld.enableDevMode()
- add link to WildFly docs

docs/reference/src/main/asciidoc/developmentmode.asciidoc

@@ -28,7 +28,7 @@ xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/
 </web-app>
 -----------------------------------------------------------------------------------------------------------
 
-NOTE: An integrator is allowed to specify an alternative way of enabling the development mode.
+NOTE: An integrator is allowed to specify an alternative way of enabling the development mode. See for example https://docs.jboss.org/author/display/WFLY/CDI+Reference#CDIReference-Developmentmode[WildFly Documentation].
 
 ==== Weld SE
 
@@ -38,15 +38,14 @@ For a Java SE application, set the system property `org.jboss.weld.development`
 java -cp myCoolApp.jar -Dorg.jboss.weld.development=true com.foo.MyMain
 -----------------------------------------------------------------------------------------------------------
 
-or use the `Weld.property()` method:
+or use the `Weld.enableDevMode()` method:
 
 [source.JAVA, java]
 -----------------------------------------------------------------
 org.jboss.weld.environment.se.Weld;
 
 public static void main(String[] args) {
-   Weld weld = new Weld().property("org.jboss.weld.development", true);
-   try (WeldContainer container = weld.initialize()) {
+   try (WeldContainer container = new Weld().enableDevMode().initialize()) {
       ...
    }
 }
@@ -70,13 +69,11 @@ You should see the following log message during initialization of your applicati
 [[probe]]
 ==== Probe
 
-This tool allows to inspect the application CDI components at runtime. See also the http://probe-weld.itos.redhat.com/weld-numberguess/weld-probe[demo application hosted on OpenShift].
-
-JSON data are available through the REST API, eventually (if <<config-dev-mode,JMX support is enabled>>) through the MXBean of name `org.jboss.weld.probe:type=JsonData,context=ID` where ID should be replaced with an idenfitier of an application.
-
-However, a default UI - HTML client (single-page application) is only available in a web application at `{webappContextPath}/weld-probe`, e.g. `http://localhost:8080/weld-numberguess/weld-probe`.
-
-Right now, the integration is provided for WildFly 10, Tomcat and Jetty (Weld Servlet) and Weld SE.
+This tool allows you to inspect the application CDI components at runtime.
+There is a default UI - HTML client (single-page application), which is only available in web applications.
+Just point your browser to `protocol://host:port/webappContextPath/weld-probe`, e.g. `http://localhost:8080/weld-numberguess/weld-probe`.
+However, it's also posible to obtain the JSON data through the REST API, eventually (if <<config-dev-mode,JMX support is enabled>>) through the MXBean of name `org.jboss.weld.probe:type=JsonData,context=ID` where ID should be replaced with an idenfitier of an application.
+Right now, Probe integration is provided for WildFly, Tomcat and Jetty (Weld Servlet), and Weld SE.
 
 TIP: There are some configuration properties which allow to tune or disable Probe features, e.g. to restrict the set of components which will be monitored. See also <<config-dev-mode>>.