fix xrefs

docs/modules/ROOT/pages/jme3/contributions/entitysystem/detailed.adoc

@@ -406,13 +406,12 @@ A lot of good things come if done “right”!
 .  Sercurity problem : No encapsulation, kind of no private POJO mean no java power in protecting data, a lot of security holes! ES implementations and COP forget all about sercurity danger as Component contracted to be processed by Processor but not hiding its content.
 .  Scale : In theory, ES should scale well..!!! But read this carefully or mislead it, enterprise system need much more than just a way to orginize your data!!!
 
-
+////
 [TIP]
 ====
 Because a lot of people find interests about the down side of ES, I've listed them carefully here xref:jme3/contributions/entitysystem/detailed/cons.adoc[cons]. After knowing the acceptable solutions from the authors, I will remove or marked the solved problem! [Peace! :p]
 ====
-
-
+////
 
 === ES consider good design in real-time app?
 

docs/modules/tutorials/pages/beginner/hello_asset.adoc

@@ -140,7 +140,7 @@ rootNode.attachChild(wall);
 
 ----
 
-In this case, you xref:ROOT:jme3/beginner/hello_material.adoc[create your own Material] and apply it to a Geometry. You base Materials on default material descriptions (such as "`Unshaded.j3md`"), as shown in this example.
+In this case, you xref:ROOT:tutorials:beginner/hello_material.adoc[create your own Material] and apply it to a Geometry. You base Materials on default material descriptions (such as "`Unshaded.j3md`"), as shown in this example.
 
 
 === Loading Text and Fonts