
**Apache Airflow version**:
1.10.13

**What happened**:
`force_logout_after` should be `force_log_out_after` in the code section https://github.com/apache/airflow/blob/master/airflow/settings.py#L372-L381. As `force_log_out_after` is actually used and written in https://github.com/apache/airflow/blob/c5700a56bb3b9a5b872bda0fe0d3de82b0128bdf/UPDATING.md#unify-user-session-lifetime-configuration.

**What you expected to happen**:
`force_logout_after` is renamed to `force_log_out_after`.
airflow/settings.py
"""
    This policy setting allows altering DAGs after they are loaded in
    the DagBag. It allows administrator to rewire some DAG's parameters.
    Alternatively you can raise ``AirflowClusterPolicyViolation`` exception
    to stop DAG from being executed.
    To define policy, add a ``airflow_local_settings`` module
    to your PYTHONPATH that defines this ``dag_policy`` function.
    Here are a few examples of how this can be useful:
    * You could enforce default user for DAGs
    * Check if every DAG has configured tags
    :param dag: dag to be mutated
    :type dag: airflow.models.dag.DAG
    """
def task_instance_mutation_hook(task_instance):