Update using_dbms_application_info.md

Doc/using_dbms_application_info.md

@@ -12,7 +12,7 @@ If you want to use this feature, make sure that tracing is set to at least `pit.
 ## Basic usage
 PIT supports both mechanisms in a user friendly way:
 
-1. Any call to `pit.enter_mandatory` automatically sets `dbms_application_info` to the actual module and method. `PIT` does not recommend to set `p_module` and `p_action` manually unless there is a strong reason to do so. Internally, `PIT` uses the package name and method name to maintain the call stack. If you set those parameters manually, they will overwrite what is sent to `dbms_application_info`, giving you the option to provide a more user friendly status on what the code is executing.
+1. Any call to `pit.enter_mandatory` automatically sets `dbms_application_info` to the actual module and method. `PIT` does not recommend to set `p_module` and `p_action` manually unless there is a strong reason to do so, such as inlining of helper methods when using `PLSQL_OPTIMIZE_LEVEL >= 2`. Internally, `PIT` uses the package name and method name to maintain the call stack. If you set those parameters manually, they will overwrite what is sent to `dbms_application_info`, giving you the option to provide a more user friendly status on what the code is executing.
 
 2. Any call to the other `pit.enter_%` methods will update `dbms_application_info` only if `p_module` or `p_action` are set manually. As long as a recursive call to `pit.enter_%` does not change the settings, the application info will stay the same as set when `pit.enter_mandatory` was called.