Fixed out of sequence title.

src/docs/asciidoc/jme3/advanced/atom_framework/design.adoc

@@ -1,6 +1,6 @@
 = design
-:author: 
-:revnumber: 
+:author:
+:revnumber:
 :revdate: 2016/03/17 20:48
 :relfileprefix: ../../../
 :imagesdir: ../../..
@@ -33,7 +33,7 @@ In this page:
 == Design goals
 
 
-==== Overal goals
+=== Overal goals
 
 *  Flexible: Game | simulations centric but not forced!
 *  Modular: Dependency injection along with Component injection
@@ -82,13 +82,13 @@ As mentioned in the Atom framwork's introduction, Atom is actually inspired by P
 So the two projects' *goals* are quite overlapped but have different focus points and mindset!
 
 *  Atom has no or less concern/ interests about mathematic/ physics correctioness ( so simmulations) but the graphics side and overal behaviors.
-*  Atom has open-source spirit… but not academic!! You can see Plotemy is quite “complicated and not very popular as it provided for academic first; in constrast, Atom is broadcasted for every one to use and to make games as kids in sandboxes. 
+*  Atom has open-source spirit… but not academic!! You can see Plotemy is quite “complicated and not very popular as it provided for academic first; in constrast, Atom is broadcasted for every one to use and to make games as kids in sandboxes.
 
 
 ==== Techniques differencies:
 
 *  Atom not “just depend on well-defined models!
-*  Atom use simplier models, …but sometime simplier is better! 
+*  Atom use simplier models, …but sometime simplier is better!
 **  Simplier Entity model (not abstract out of Java object)
 **  Actor model is not as abstrat also actually from threaded enviroment
 **  No contract in Systems, the study of Systems conections and interactivities are though data-driven analysising only, that's it, a dataflow monitoring system over working system.
@@ -140,20 +140,20 @@ For example, AtomCore module depends in these high quality libraries:
 
 *  JME3
 *  Common Java JSR annotations:
-*  Apache commons 
+*  Apache commons
 **  Lang
 **  Configurations
 **  BeanUtils
 **  Collections
 
-*  Google's 
+*  Google's
 **  Guava:
 **  Guice: Dependency injection
 **  Snappy:
 **  LevelDB
 **  Auto
 
-*  
+*
 
 Other require pieces are write from sk
 
@@ -170,7 +170,7 @@ This section is dedicated to explain some idioms, patterns, and long term soluti
 
 From an abstraction level, a Game- a special kind of software (almost always):
 
-*  composed by Entities, and their Stage; 
+*  composed by Entities, and their Stage;
 *  where Actions happen in a Cycle, procedure Events;
 
 A little bit more detailed, Gameplay is the way player play the Game, has:
@@ -184,8 +184,8 @@ A little bit more detailed, Gameplay is the way player play the Game, has:
 **  Interactive mode: When player interact with the game world
 
 *  Control: The way player handle their entities
-*  League: 
-**  Single: Infos, score, rewards stick to an individual 
+*  League:
+**  Single: Infos, score, rewards stick to an individual
 **  Multi: The way players join, left, make friend and interactive and play together…
 
 *  Status: Way to pause/continue , save/load current game
@@ -256,7 +256,7 @@ At some point, we have to find a solution to reduce “manual Data + code making
 
 [NOTE]
 ====
-This is so important to mention that every techs Atom framework are around Bean/ POJO technologies. 
+This is so important to mention that every techs Atom framework are around Bean/ POJO technologies.
 ====
 
 For example:
@@ -273,7 +273,7 @@ As built in Java technologies, Bean/ POJO is the only "consider good" solution a
 ....
 
 ....
-also can be seen as 
+also can be seen as
 **from Object oriented programming to Data oriented programming**
 **from Object oriented programming to Aspect oriented programming**
 ....
@@ -343,10 +343,10 @@ link:http://code.imagej.net/gbh/lookup/DependencyInjectionandLookup.html[http://
 ==== Dependency management coolness
 
 So what's cool about dependency in real-time application and game that Atom included…
-A lot of things, but let me point out fews: 
+A lot of things, but let me point out fews:
 
 *Real-time dependency* is a new feature for game developing…
-Imagine that even the game just can load part of assets, with the other are delayed or missing, the dependency graph can help the game cycle continue to run, part of it in the mean time. 
+Imagine that even the game just can load part of assets, with the other are delayed or missing, the dependency graph can help the game cycle continue to run, part of it in the mean time.
 
 In fact the dependency graph can be considered the topo structure of JME assets dependency graph before it built, means hard links via references. Now even when the assets graph are just partly loaded, the game can run because it know a resolution to safety resolve the assets graph and scene graph afterward.
 
@@ -359,7 +359,7 @@ You can imagine how Atom framework tend to bridge JME game and the Web universal
 
 ==== Services, Dependency and Decoupling
 
-The world of enteprise evolve Modular paradigm a lot to link services (database, configurations, network protocols, web…) and help they work together in one application. 
+The world of enteprise evolve Modular paradigm a lot to link services (database, configurations, network protocols, web…) and help they work together in one application.
 
 
 === Available Services