Updated README.md

Author: agnostic-apollo

README.md

@@ -6,17 +6,17 @@
 
 ### Contents:
 - [Project Details](#Project-Details)
-- [How Project Works](###How-Project-Works)
-- [Activity States And Transitions](###Activity-States-And-Transitions)
-- [Dependencies](###Dependencies)
-- [Downloads](###Downloads)
-- [Install Instructions For Termux In Android](###Install-Instructions-For-Termux-In-Android)
-- [Usage](###Usage)
-- [Current Features](###Current-Features)
-- [Planned Features](###Planned-Features)
-- [Issues](###Issues)
-- [Worthy of Note](###Worthy-of-Note)
-- [Finding Device Specific Logcat Entries](###Finding-Device-Specific-Logcat-Entries)
+- [How Project Works](#How-Project-Works)
+- [Activity States And Transitions](#Activity-States-And-Transitions)
+- [Dependencies](#Dependencies)
+- [Downloads](#Downloads)
+- [Install Instructions For Termux In Android](#Install-Instructions-For-Termux-In-Android)
+- [Usage](#Usage)
+- [Current Features](#Current-Features)
+- [Planned Features](#Planned-Features)
+- [Issues](#Issues)
+- [Worthy of Note](#Worthy-of-Note)
+- [Finding Device Specific Logcat Entries](#Finding-Device-Specific-Logcat-Entries)
 ##
 
 
@@ -83,7 +83,7 @@ Once it is found if the activity is fullscreen or not, then the current activity
 
 The 3 profiles above call the `Activity State Change Relay` Task that finds the currently opened package and activity for `activity_start` activity_state_change, either from `%lc_text` or with other ways mentioned earlier. Then it sets the `%ActivityStateChangeControllerCommand` variable with the `%current_package_and_activity` and `%activity_state_change` values which triggers the `Activity State Change Controller Command Monitor` Profile which calls the `Activity State Change Controller` Task to further process the activity state change and call any other required tasks for respected packages and activities. Note that either `ActivityTrigger Activity Start Monitor` or `Custom Activity Start Monitor` must be activated at the same time. If they are both activated, then this can cause duplication and result in fake transitions. 
 
-The `Activity State Change Controller` Task first checks if the current_package_and_activity passed is a valid package and activity name in the format `package_name/activity_name`. If it is then it checks if the current activity is in fullscreen mode with status bars hidden. Then it sets the `current_activity_state` depending on `activity_state_change` and `fullscreen_mode`. Then it checks if the a `package_name Activity State Change Responder` Task exists in the Tasker config for the `current_package_and_activity` or `previous_package_and_activity`. If either of those exists, then it calculates the `previous_activity_task_activity_transition_par` and `current_activity_task_activity_transition_par` depending on activity transitions in the transitions table defined in [Activity States And Transitions](###Activity-States-And-Transitions). Then it calls the `previous_package Activity State Change Responder` Task if it exists with the `previous_activity` as `%par1` and `previous_activity_task_activity_transition_par` as `%par2`. Then it calls the `current_package Activity State Change Responder` Task if it exists with the `current_activity` as `%par1` and `current_activity_task_activity_transition_par` as `%par2`. Those tasks may respond appropriately to activity transitions but must not perform long running operations since this task will not finish until the called tasks are finished to maintain order and any queued tasks for this task will also be in waiting. Any long running operations that do not require ordered execution can be run inside the called tasks in additional tasks with `%priority - 1` so that the called tasks can return before the additional tasks finish.
+The `Activity State Change Controller` Task first checks if the current_package_and_activity passed is a valid package and activity name in the format `package_name/activity_name`. If it is then it checks if the current activity is in fullscreen mode with status bars hidden. Then it sets the `current_activity_state` depending on `activity_state_change` and `fullscreen_mode`. Then it checks if the a `package_name Activity State Change Responder` Task exists in the Tasker config for the `current_package_and_activity` or `previous_package_and_activity`. If either of those exists, then it calculates the `previous_activity_task_activity_transition_par` and `current_activity_task_activity_transition_par` depending on activity transitions in the transitions table defined in [Activity States And Transitions](#Activity-States-And-Transitions). Then it calls the `previous_package Activity State Change Responder` Task if it exists with the `previous_activity` as `%par1` and `previous_activity_task_activity_transition_par` as `%par2`. Then it calls the `current_package Activity State Change Responder` Task if it exists with the `current_activity` as `%par1` and `current_activity_task_activity_transition_par` as `%par2`. Those tasks may respond appropriately to activity transitions but must not perform long running operations since this task will not finish until the called tasks are finished to maintain order and any queued tasks for this task will also be in waiting. Any long running operations that do not require ordered execution can be run inside the called tasks in additional tasks with `%priority - 1` so that the called tasks can return before the additional tasks finish.
 
 The `Reset Activity State Change Variables On Monitor Start` Profile is called by the `Reset Activity State Change Variables On Monitor Start` Task when Tasker Monitor is started. It should ideally also be manually called when the `* Activity Start Monitor` and `* Activity Config Change Monitor` tasks are enabled/disabled. Resetting variables is required to prevent false activity transitions if activity states were stopped from being monitor either by tasker being killed or manually by the user.