rename programmatic to focused

Author: dmelikyan

README.md

@@ -79,14 +79,14 @@ All initialization options:
 * `app_version` (Optional) Sets application version, which can be used to associate profiling information with the source code release.
 * `app_environment` (Optional) Used to differentiate applications in different environments.
 * `host_name` (Optional) By default, host name will be the OS hostname.
-* `auto_profiling` (Optional) If set to `False`, disables automatic profiling and reporting. Programmatic or manual profiling should be used instead. Useful for environments without support for timers or background tasks.
+* `auto_profiling` (Optional) If set to `False`, disables automatic profiling and reporting. Focused or manual profiling should be used instead. Useful for environments without support for timers or background tasks.
 * `debug` (Optional) Enables debug logging.
 * `cpu_profiler_disabled`, `allocation_profiler_disabled`, `block_profiler_disabled`, `error_profiler_disabled` (Optional) Disables respective profiler when `True`.
 * `include_agent_frames` (Optional) Set to `True` to not exclude agent stack frames from profile call graphs.
 * `auto_destroy` (Optional) Set to `False` to disable agent's exit handlers. If necessary, call `destroy()` to gracefully shutdown the agent.
 
 
-#### Programmatic profiling
+#### Focused profiling
 
 Use `agent.profile(name)` to instruct the agent when to start and stop profiling. The agent decides if and which profiler is activated. Normally, this method should be used in repeating code, such as request or event handlers. In addition to more precise profiling, timing information will also be reported for the profiled spans. Usage example:
 

README.rst

@@ -114,8 +114,8 @@ All initialization options:
 -  ``host_name`` (Optional) By default, host name will be the OS
    hostname.
 -  ``auto_profiling`` (Optional) If set to ``False``, disables automatic
-   profiling and reporting. Programmatic or manual profiling should be
-   used instead. Useful for environments without support for timers or
+   profiling and reporting. Focused or manual profiling should be used
+   instead. Useful for environments without support for timers or
    background tasks.
 -  ``debug`` (Optional) Enables debug logging.
 -  ``cpu_profiler_disabled``, ``allocation_profiler_disabled``,
@@ -127,8 +127,8 @@ All initialization options:
    handlers. If necessary, call ``destroy()`` to gracefully shutdown the
    agent.
 
-Programmatic profiling
-^^^^^^^^^^^^^^^^^^^^^^
+Focused profiling
+^^^^^^^^^^^^^^^^^
 
 Use ``agent.profile(name)`` to instruct the agent when to start and stop
 profiling. The agent decides if and which profiler is activated.