[analysis api] rename ValidityToken -> KtLifetimeToken

docs/analysis/analysis-api/analysis-api-usage.md

@@ -19,7 +19,7 @@ fun KtAnalysisSession.getSymbol() : KtSymbol {
 }
 ```
 
-## No leakages of ValidityTokenOwners from KtAnalysisSession context
-All `ValidityTokenOwners` you get inside a `KtAnalysisSessoin` context should never leak it. But you may:
-* Store your `ValidityTokenOwners` as a field inside a class that implements `ValidityTokenOwners`. This way your outer class is `ValidityTokenOwners` itself and all rules apply to it. 
+## No leakages of KtLifetimeTokenOwners from KtAnalysisSession context
+All `KtLifetimeTokenOwners` you get inside a `KtAnalysisSessoin` context should never leak it. But you may:
+* Store your `KtLifetimeTokenOwners` as a field inside a class that implements `KtLifetimeTokenOwners`. This way your outer class is `KtLifetimeTokenOwners` itself and all rules apply to it. 
 * Pass it to another function with a `KtAnalysisSessoin` receiver.

docs/analysis/analysis-api/analysis-api.md

@@ -50,11 +50,11 @@ Where `action` lambda represents the **KtAnalysisSession Scope**.
 
 ## Lifecycle Owners
 
-Every Lifecycle Owner has its lifecycle which is defined by corresponding `ValidityToken`. There is a special
+Every Lifecycle Owner has its lifecycle which is defined by corresponding `KtLifetimeToken`. There is a special
 function `analyseWithCustomToken` which allows specifying needed behaviour. There are also analyse function which is made for the IDE which
-analyses with `ReadActionConfinementValidityToken`
+analyses with `KtReadActionConfinementLifetimeToken`
 
-`ReadActionConfinementValidityToken` has the following contracts:
+`KtReadActionConfinementLifetimeToken` has the following contracts:
 
 * Accessibility contracts
     * Analysis should not be called from **EDT Thread**