Fix formatting

enginmanap · Jan 12, 2019 · fd25e6b · fd25e6b
1 parent 7e4a2c0
commit fd25e6b
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 8 deletions.
diff --git a/docs/ExtendingByAPI/implementAIActor.rst b/docs/ExtendingByAPI/implementAIActor.rst
@@ -127,6 +127,7 @@ InformationRequest struct
 _________________________
 
 This struct is part of ActorInterface, and each frame Limon Engine checks all Actors for request changes. When a request is checked, its information will be reset to prevent multiple requests.
+
 +------------------------+-----------------------------+--------------------------------------------------------------------------+
 | Type                   | Name                        | Description                                                              |
 +------------------------+-----------------------------+--------------------------------------------------------------------------+
@@ -143,11 +144,12 @@ How to enable Dynamic Library discovery
 _______________________________________
 
 Limon engine will try to load custom actors on engine startup, from libcustomTriggers file (extension based on platform). If the file is found, engine will check for a method with following signature:
+::
 
-``void registerActors(std::map<std::string, ActorInterface*(*)(uint32_t, LimonAPI*)>* actorMap)``
+    void registerActors(std::map<std::string, ActorInterface*(*)(uint32_t, LimonAPI*)>* actorMap)
 
 This method should fill the actorMap passed, with all the custom actors, like this:
 ::
 
-    (*actorMap)["$ACTORNAME1$"] = &createActorT<$ActorClass1$>;
-    (*actorMap)["$ACTORNAME2$"] = &createActorT<$ActorClass2$>;
+    (*actorMap)["$ACTOR_NAME1$"] = &createActorT<$ActorClass1$>;
+    (*actorMap)["$ACTOR_NAME2$"] = &createActorT<$ActorClass2$>;
diff --git a/docs/ExtendingByAPI/implementAction.rst b/docs/ExtendingByAPI/implementAction.rst
@@ -74,12 +74,11 @@ _______________________________________
 
 Limon engine will try to load custom actions on engine startup, from libcustomTriggers file (extension based on platform). If the file is found, engine will check for a method with following signature:
 
-
-``void registerAsTrigger(std::map<std::string, TriggerInterface*(*)(LimonAPI*)>* triggerMap)``
+::
+    void registerAsTrigger(std::map<std::string, TriggerInterface*(*)(LimonAPI*)>* triggerMap)
 
 This method should fill the triggerMap passed, with all the custom actions, like this:
-
-``
+::
     (*triggerMap)["$ACTION_NAME1$"] = &createT<$ActionClass1$>;
     (*triggerMap)["$ACTION_NAME2$"] = &createT<$ActionClass2$>;
-``
+