fix links

Author: dimaMachina

.husky/pre-push

@@ -1 +1 @@
-yarn lint
+pnpm lint

website/src/pages/docs/custom-rules.mdx

@@ -24,7 +24,7 @@ the AST nodes you wish to visit. It can either be a
 or a complex [ESLint selector](https://eslint.org/docs/developer-guide/selectors) that allows you to
 travel and filter AST nodes.
 
-We recommend you to read the [graphql-eslint parser documentation](parser.md) before getting
+We recommend you to read the [graphql-eslint parser documentation](/docs/getting-started/parser) before getting
 started, to understand the differences between the AST structures.
 
 The `graphql-eslint` comes with a TypeScript wrapper for ESLint rules, and provides a testkit to
@@ -71,7 +71,7 @@ rules. It coverts most of the use-cases and concepts of rules.
 Since our parser converts GraphQL AST to ESTree structure, there are some minor differences in the
 structure of the objects. If you are using TypeScript, and you typed your rule with
 `GraphQLESLintRule` - you'll see that each `node` is a bit different from the AST nodes of GraphQL
-(you can read more about that in [graphql-eslint parser documentation](parser.md)).
+(you can read more about that in [graphql-eslint parser documentation](/docs/getting-started/parser)).
 
 If you need access to the original GraphQL AST `node`, you can use `.rawNode()` method on each node
 you get from the AST structure of ESLint.

website/src/pages/rules/deprecated-rules.mdx

@@ -2,23 +2,23 @@
 
 ## `avoid-duplicate-fields`
 
-This rule was renamed to [`no-duplicate-fields`](rules/no-duplicate-fields.md).
+This rule was renamed to [`no-duplicate-fields`](/rules/no-duplicate-fields).
 
 ## `avoid-scalar-result-type-on-mutation`
 
 This rule was renamed to
-[`no-scalar-result-type-on-mutation`](rules/no-scalar-result-type-on-mutation.md).
+[`no-scalar-result-type-on-mutation`](/rules/no-scalar-result-type-on-mutation).
 
 ## `avoid-typename-prefix`
 
-This rule was renamed to [`no-typename-prefix`](rules/no-typename-prefix.md).
+This rule was renamed to [`no-typename-prefix`](/rules/no-typename-prefix).
 
 ## `avoid-operation-name-prefix`
 
 This rule was removed because the same things can be validated using
-[`naming-convention`](rules/naming-convention.md).
+[`naming-convention`](/rules/naming-convention).
 
 ## `no-operation-name-suffix`
 
 This rule was removed because the same things can be validated using
-[`naming-convention`](rules/naming-convention.md).
+[`naming-convention`](/rules/naming-convention).