Update guides/relationships/features/links-mode.md

runspired · gitKrystan · web-flow · commit 40c43546bacd · 2025-03-12T20:47:58.000-07:00
Co-authored-by: Krystan HuffMenne &lt;kmenne+github@gmail.com&gt;
diff --git a/guides/relationships/features/links-mode.md b/guides/relationships/features/links-mode.md
@@ -122,7 +122,7 @@ export default class User extends Model {
 }
 ```
 
-This works for both `async` and `non-async` relationships and only changes the fetching behavior of the field it is defined on. So for instance, in the example above, `homeAddress` is fetched in links mode while `<Address>.residents` might still be using the legacy adapter experience.
+This works for both `async` and `non-async` relationships and only changes the fetching behavior of the field it is defined on. For instance, in the example above, `homeAddress` is fetched in links mode while `<Address>.residents` might still be using the legacy adapter experience.
 
 ### For A SchemaRecord in LegacyMode
 

Original file line number	Diff line number	Diff line change
`@@ -122,7 +122,7 @@ export default class User extends Model {`
`122`	`122`	`}`
`123`	`123`	```
`124`	`124`
`125`		-This works for both `async` and `non-async` relationships and only changes the fetching behavior of the field it is defined on. So for instance, in the example above, `homeAddress` is fetched in links mode while `<Address>.residents` might still be using the legacy adapter experience.
	`125`	+This works for both `async` and `non-async` relationships and only changes the fetching behavior of the field it is defined on. For instance, in the example above, `homeAddress` is fetched in links mode while `<Address>.residents` might still be using the legacy adapter experience.
`126`	`126`
`127`	`127`	`### For A SchemaRecord in LegacyMode`
`128`	`128`