fix links

docs/modules/core/pages/app/statsview.adoc

@@ -1,10 +1,6 @@
 = Optimizing Your Game Using Statistics
-:author:
-:revnumber:
-:revdate: 2016/03/17 20:48
-:relfileprefix: ../../
-:imagesdir: ../..
-ifdef::env-github,env-browser[:outfilesuffix: .adoc]
+:revnumber: 2.0
+:revdate: 2020/07/23
 
 
 When you create a SimpleApplication, you see the default StatsView and FpsView in the left corner.
@@ -108,8 +104,6 @@ What goal are you trying to achieve in general?
 .  The FPS should be 30 or more on the slowest hardware that you target.
 .  10'000-50'000 vertices is a typical average value for a scene.
 
-'''
-
 See also:
 
 *  link:https://hub.jmonkeyengine.org/t/good-triangles-count/22843[What's a good triangle count?] Forum discussion

docs/modules/tutorials/pages/concepts/faq.adoc

@@ -604,7 +604,7 @@ Use a PhysicsControl's hinges and joints.
 
 === What are these FPS/Objects/Vertices/Triangles statistics?
 
-At the bottom left of every default SimpleGame, you see the xref:ROOT:jme3/advanced/statsview.adoc[StatsView] and the FPS (frames per seconds) view. These views provide you with extra information during the development phase. For example, if you notice the object count is increasing and the FPS is decreasing, then you know that your code attaches too many objects and does not detach enough of them again (maybe a loop gone wild?).
+At the bottom left of every default SimpleGame, you see the xref:core:app/statsview.adoc[StatsView] and the FPS (frames per seconds) view. These views provide you with extra information during the development phase. For example, if you notice the object count is increasing and the FPS is decreasing, then you know that your code attaches too many objects and does not detach enough of them again (maybe a loop gone wild?).
 
 
 === How do I get rid of the FPS/Objects statistics?

docs/modules/tutorials/pages/concepts/optimization.adoc

@@ -60,4 +60,4 @@ The StatsView counts Objects,Uniforms,Triangles,Vertices are in the scene, and i
 
 For example, `Textures (M)` tells you how many textures are currently in OpenGL memory.
 
-Generally jME3 is well optimized and optimizes these things correctly. Read xref:ROOT:jme3/advanced/statsview.adoc[statsview] to learn the details about how to interpret the statistics, how to tell whether your values are off, or whether they point out a problem.
+Generally jME3 is well optimized and optimizes these things correctly. Read xref:core:app/statsview.adoc[statsview] to learn the details about how to interpret the statistics, how to tell whether your values are off, or whether they point out a problem.