fix links

Author: dimaMachina

pnpm-lock.yaml

@@ -16,7 +16,7 @@
     "@monaco-editor/react": "4.4.6",
     "@radix-ui/react-icons": "1.1.1",
     "@radix-ui/react-select": "1.1.2",
-    "@theguild/components": "4.5.0",
+    "@theguild/components": "4.5.1",
     "clsx": "1.2.1",
     "graphql": "16.6.0",
     "lodash.debounce": "4.0.8",

website/package.json

@@ -24,8 +24,8 @@ 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](/docs/getting-started/parser) before getting
-started, to understand the differences between the AST structures.
+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
 simplify testing process with GraphQL schemas, so you can use that by importing `GraphQLESLintRule`
@@ -71,7 +71,8 @@ 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](/docs/getting-started/parser)).
+(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/docs/custom-rules.mdx

@@ -104,7 +104,8 @@ configuration file:
 }
 ```
 
-> You can find a complete [documentation of the `parserOptions` here](/docs/parser-options).
+> You can find a complete
+> [documentation of the `parserOptions` here](/docs/getting-started/parser-options).
 
 > Some rules require type information to operate, it's marked in the docs for each rule!
 

website/src/pages/docs/getting-started.mdx

@@ -61,7 +61,7 @@ schema. The parser uses `graphql-tools` and it's loaders, that means you can eit
 path to a local `.json` (introspection) file, or a path to a local `.graphql` file(s). You can also
 use Glob expressions to load multiple files.
 
-[You can find more detail on the `parserOptions` config here](/docs/parser-options).
+[You can find more detail on the `parserOptions` config here](/docs/getting-started/parser-options).
 
 Providing the schema will make sure that rules that needs it will be able to access it, and it
 enriches every converted AST node with `typeInfo`.