Review doc by the AI

Author: dprevost-LMI

docs/CustomMatchers.md

@@ -2,8 +2,8 @@
 
 Similar to how `expect-webdriverio` extends Jasmine/Jest matchers it's possible to add custom matchers.
 
-- Jasmine see [custom matchers](https://jasmine.github.io/tutorials/custom_matchers) doc
-- Everyone else see Jest's [expect.extend](https://jestjs.io/docs/en/expect#expectextendmatchers)
+- [Jasmine](https://jasmine.github.io/) see [custom matchers](https://jasmine.github.io/tutorials/custom_matchers) doc
+- Everyone else see [Jest's expect.extend](https://jestjs.io/docs/en/expect#expectextendmatchers)
 
 Custom matchers should be added in wdio `before` hook
 

docs/Framework.md

@@ -10,9 +10,9 @@ We can pair `expect-webdriverio` with [Jest](https://jestjs.io/), [Mocha](https:
 
 ### Jest
 We can use `expect-webdriverio` with [Jest](https://jestjs.io/) with either the [`@jest/globals`](https://www.npmjs.com/package/@jest/globals) (preferred) or the [`@types/jest`](https://www.npmjs.com/package/@types/jest) (has global imports support)
-  - Note: Jest maintainers do not support `@types/jest`. In case this library gets out of date or has problems, support might be dropped.
+  - Note: Jest maintainers do not support [`@types/jest`](https://www.npmjs.com/package/@types/jest). In case this library gets out of date or has problems, support might be dropped.
 
-In each case, when used <u>**outside of [WDIO Testrunner](https://webdriver.io/docs/clioptions)**</u>, types are required to be added in your `tsconfig.json`
+In each case, when used <u>**outside of [WDIO Testrunner](https://webdriver.io/docs/clioptions)**</u>, types are required to be added in your [`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
   - Note: With Jest the matchers `toMatchSnapshot` and `toMatchInlineSnapshot` were overloaded. To resolve correctly the types `expect-webdriverio/jest` must be last.
 
 #### With `@jest/globals`
@@ -95,15 +95,15 @@ Expected in `tsconfig.json`:
 ```
 
 #### Chai
-TODO - Integration with [Chai](https://www.chaijs.com/) assertion library
+TODO - Integration with [Chai](https://www.chaijs.com/) assertion library. See [`@types/chai`](https://www.npmjs.com/package/@types/chai) for type definitions.
 
 ### Jasmine
 When paired with [Jasmine](https://jasmine.github.io/), [`@wdio/jasmine-framework`](https://www.npmjs.com/package/@wdio/jasmine-framework) is also required to have it configured correctly as it needs to force the `expect` to be `expectAsync` and also to register the wdio matchers with `addAsyncMatcher` since `expect-webdriverio` only supports the jest style `expect.extend` version.
 
 The types `expect-webdriverio/jasmine` is still offers but subject to removal or to be moved into `@wdio/jasmine-framework`. The usage of `expectAsync` is also subject to future removal.
 
 #### Jasmine `expectAsync`
-Since the above types augment the `AsyncMatcher` of `Jasmine` then with this library alone it look like the below even though it is not runnable since the matcher are not registered
+Since the above types augment the `AsyncMatcher` of `Jasmine` then with this library alone it looks like the below even though it is not runnable since the matchers are not registered
 
 ```ts
 describe('My tests', async () => {
@@ -156,7 +156,7 @@ Expected in `tsconfig.json`:
 ```
 
 #### Asymmetric matcher 
-Asymmetric matcher has limited support, even though `jasmine.stringContaining` has not error it is potential not working even with `@wdio/jasmine-framework`, but the below should:
+Asymmetric matcher has limited support, even though `jasmine.stringContaining` has no error it is potentially not working even with `@wdio/jasmine-framework`, but the below should:
 
 ```ts
 describe('My tests', async () => {

docs/Types.md

@@ -4,14 +4,14 @@
 If you are using the [WDIO Testrunner](https://webdriver.io/docs/clioptions) everything will be automatically setup. Just follow the [setup guide](https://webdriver.io/docs/typescript#framework-setup) from the docs. However if you run WebdriverIO with a different testrunner or in a simple Node.js script you will need to add `expect-webdriverio` to `types` in the `tsconfig.json`.
 
 - `"expect-webdriverio"` for everyone except Jasmine/Jest users.
-- `"expect-webdriverio/jasmine"` for Jasmine
-- `"expect-webdriverio/jest"` for Jest
+- `"expect-webdriverio/jasmine"` for [Jasmine](https://jasmine.github.io/)
+- `"expect-webdriverio/jest"` for [Jest](https://jestjs.io/)
 - `"expect-webdriverio/expect-global"` // Optional, if you wish to use expect of `expect-webdriverio` globally without explicit import
   - Note: Same as the former `"expect-webdriverio/types"`, now deprecated!
 
 ## JavaScript (VSCode)
 
-It's required to create `jsconfig.json` in project root and refer to the type definitions to make autocompletion work in vanilla js.
+It's required to create [`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig) in project root and refer to the type definitions to make autocompletion work in vanilla js.
 
 ```json
 {
@@ -24,7 +24,7 @@ It's required to create `jsconfig.json` in project root and refer to the type de
 ```
 
 ## Jasmine special case
-Jasmine is different from Jest or the standard `expect` definition since it supports promises using `expectAsync` which make it quite challenging.
+[Jasmine](https://jasmine.github.io/) is different from [Jest](https://jestjs.io/) or the standard `expect` definition since it supports promises using `expectAsync` which makes it quite challenging.
 
 Even though this library by itself is not fully Jasmine-ready, it offers the types of the matcher only on the `AsyncMatcher` since using `jasmine.expect` does not work out-of-the-box. However, if you are pulling on the `expect` of `expect-webdriverio`, you will be able to have the WebDriverIO matcher types on `expect`. 
 
@@ -33,4 +33,4 @@ Support of `expectAsync` keyword is subject to change and may be dropped in the
 ### Dependency on `@wdio/jasmine-framework`
 As mentioned above, this library alone is not working with Jasmine. It is required to manually do some tweaks, or it is strongly recommended to also pair it with `@wdio/jasmine-framework`. See [Framework.md](Framework.md) for more information.
 
-When using `@wdio/jasmine-framework`, since it replaces `jasmine.expect` with `jasmine.expectAsync`, then matchers are usable on the keyword `expect`, but still typing on `expect` directly from Jasmine namespace is not supported as of today!
+When using [`@wdio/jasmine-framework`](https://www.npmjs.com/package/@wdio/jasmine-framework), since it replaces `jasmine.expect` with `jasmine.expectAsync`, then matchers are usable on the keyword `expect`, but still typing on `expect` directly from [Jasmine](https://jasmine.github.io/) namespace is not supported as of today!