Compatibility doc (2)

Author: Denis Hilt

README.md

@@ -8,17 +8,29 @@ Unlimited bidirectional virtual scrolling over limited viewport. A directive for
 <p dir="rtl">
 <sub>can donate? go <b><a href="https://github.com/dhilt/ngx-ui-scroll?sponsor=1">here</a></b></sub><sub> 👉 <br>make open-source world better</sub></p>
 
+- [Compatibility](#compatibility)
 - [Motivation](#motivation)
 - [Features](#features)
 - [Getting](#getting)
 - [Usage](#usage)
 - [Settings](#settings)
 - [Adapter API](#adapter-api)
-- [Compatibility](#compatibility)
 - [Development](#development)
 
 <br>
 
+<a name="compatibility" id="compatibility"></a>
+### Compatibility
+
+|ngx-ui-scroll|Angular|compiled|support|notes|
+|:--|:--|:--|:--|:--|
+|v1|5-12|View Engine|no|no dependencies (vscroll is not extracted)|
+|v2|5-12|View Engine|maintenance|vscroll is a bundle-dependency|
+|v3|12+|Ivy|active|vscroll is a peer-dependency|
+
+So if the consumer app is view-engine compatible, you should use v2 which is in maintenance mode and under [v2-legacy](https://github.com/dhilt/ngx-ui-scroll/tree/v2-legacy) branch.
+
+
 ### Motivation
 
 Scrolling large datasets may cause performance issues. Many DOM elements, many data-bindings, many event listeners... The common way to improve the performance is to render only a small portion of the dataset visible to a user. Other dataset elements that are not visible to a user are virtualized with upward and downward empty padding elements which should provide a consistent viewport with consistent scrollbar parameters.
@@ -226,16 +238,6 @@ console.log('Two-phase replacement done');
 For more information, see [Adapter demo page](https://dhilt.github.io/ngx-ui-scroll/#adapter).
 
 
-<a name="compatibility" id="compatibility"></a>
-### Compatibility
-
-|ngx-ui-scroll|Angular|compiled|support|notes|
-|:--|:--|:--|:--|:--|
-|1|5-12|View Engine|no|no dependencies|
-|2|5-12|View Engine|maintenance|vscroll is bundle-dependency|
-|3|12+|Ivy|active|vscroll is peer-dependency|
-
-
 ### Development
 
 There are some npm scripts available from package.json:
@@ -273,7 +275,7 @@ Also, there are some environment variables for additional customization of the d
 
 |Name|Value|Description|
 |:--|:----|:----------|
-|DEV_SERVER_PORT|4200|Port the dev server (webpack) will use. Need to run `npm run start:env` instead of `npm run` to make this setting work.|
+|DEV_SERVER_PORT|4200|Port the dev server (webpack) will use. Need to run `npm run start-env` instead of `npm run` to make this setting work.|
 |TEST_BROWSER|default&nbsp;&#124; chrome&nbsp;&#124; firefox|Platform for running tests. By default a headless chrome is used; "chrome" or "firefox" are for running tests in real (chrome/ff) browser |
 |TEST_SERVER_PORT|9876|Port that will be used by non-default testing browser |