mirumee
diff --git a/‎docs/07-improving-import-performance.md‎ ‎…uides/13-improving-import-performance.md‎docs/07-improving-import-performance.md renamed to docs/02-guides/13-improving-import-performance.md
Lines changed: 1 addition & 1 deletion b/‎docs/07-improving-import-performance.md‎ ‎…uides/13-improving-import-performance.md‎docs/07-improving-import-performance.md renamed to docs/02-guides/13-improving-import-performance.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎…s/08-fragments-and-forward-references.md‎ ‎…s/14-fragments-and-forward-references.md‎docs/08-fragments-and-forward-references.md renamed to docs/02-guides/14-fragments-and-forward-references.md b/‎…s/08-fragments-and-forward-references.md‎ ‎…s/14-fragments-and-forward-references.md‎docs/08-fragments-and-forward-references.md renamed to docs/02-guides/14-fragments-and-forward-references.md
@@ -30,4 +30,4 @@ Both options are opt-in, and neither changes generated code until you set it: a
 
 `use_alias_generator` does not change what any field is called on the wire. Names that `to_camel` cannot reconstruct keep an explicit `Field(alias=...)`: `__typename`, keyword-escaped names such as `list_`, acronyms such as `productID`, and schemas whose fields are already snake_case (`some_field` would otherwise become `someField`). The same holds with `convert_to_snake_case = false`, where field names already match the schema and every renamed field keeps its alias - which also means there is nothing to gain there, so leave `use_alias_generator` off unless you convert to snake_case.
 
-Two caveats. `defer_model_build` moves the build cost to first use rather than removing it, so a short-lived process that touches every model pays it anyway. And because `alias_generator` is set on the shared `BaseModel`, it also applies to fields you add through [custom mixins](https://github.com/mirumee/ariadne-codegen/blob/main/README.md#extending-models-with-custom-mixins) - name those in snake_case and they will be aliased to camelCase.
+Two caveats. `defer_model_build` moves the build cost to first use rather than removing it, so a short-lived process that touches every model pays it anyway. And because `alias_generator` is set on the shared `BaseModel`, it also applies to fields you add through [custom mixins](./07-extending-types.md#extending-models-with-custom-mixins) - name those in snake_case and they will be aliased to camelCase.
Original file line number	Diff line number	Diff line change
`@@ -30,4 +30,4 @@ Both options are opt-in, and neither changes generated code until you set it: a`
`30`	`30`
`31`	`31`	`use_alias_generator` does not change what any field is called on the wire. Names that `to_camel` cannot reconstruct keep an explicit `Field(alias=...)`: `__typename`, keyword-escaped names such as `list_`, acronyms such as `productID`, and schemas whose fields are already snake_case (`some_field` would otherwise become `someField`). The same holds with `convert_to_snake_case = false`, where field names already match the schema and every renamed field keeps its alias - which also means there is nothing to gain there, so leave `use_alias_generator` off unless you convert to snake_case.
`32`	`32`
`33`		-Two caveats. `defer_model_build` moves the build cost to first use rather than removing it, so a short-lived process that touches every model pays it anyway. And because `alias_generator` is set on the shared `BaseModel`, it also applies to fields you add through [custom mixins](https://github.com/mirumee/ariadne-codegen/blob/main/README.md#extending-models-with-custom-mixins) - name those in snake_case and they will be aliased to camelCase.
	`33`	+Two caveats. `defer_model_build` moves the build cost to first use rather than removing it, so a short-lived process that touches every model pays it anyway. And because `alias_generator` is set on the shared `BaseModel`, it also applies to fields you add through [custom mixins](./07-extending-types.md#extending-models-with-custom-mixins) - name those in snake_case and they will be aliased to camelCase.