docs: add back ticks and adjust wording

docs/route/client-action.md

@@ -22,7 +22,7 @@ export const clientAction = async ({
 
 This function is only ever run on the client, and can be used in a few ways:
 
-- Instead of a server action for full-client routes
+- Instead of a server `action` for full-client routes
 - To use alongside a `clientLoader` cache by invalidating the cache on mutations
 - To facilitate a migration from React Router
 

docs/route/client-loader.md

@@ -25,7 +25,7 @@ export const clientLoader = async ({
 
 This function is only ever run on the client, and can be used in a few ways:
 
-- Instead of a server loader for full-client routes
+- Instead of a server `loader` for full-client routes
 - To use alongside a `clientLoader` cache by invalidating the cache on mutations
   - Maintaining a client-side cache to skip calls to the server
   - Bypassing the Remix [BFF][bff] hop and hitting your API directly from the client
@@ -58,7 +58,7 @@ export default function Component() {
 
 ### `clientLoader.hydrate`
 
-If you need to run your `clientLoader` on hydration, you can opt-into that by setting `clientLoader.hydrate=true`. This will tell Remix that it needs to run the `clientLoader` on hydration. Without a `HydrateFallback`, your route component will be SSR'd with the server loader data - and then `clientLoader` will run and the returned data will be updated in-place in the hydrated route Component.
+If you need to run your `clientLoader` on hydration, you can opt-in by setting `clientLoader.hydrate=true`. This will tell Remix that it needs to run the `clientLoader` on hydration. Without a `HydrateFallback`, your route component will be SSR'd with the server `loader` data - and then `clientLoader` will run and the returned data will be updated in-place in the hydrated route Component.
 
 <docs-info>If a route exports a `clientLoader` and does not export a server `loader`, then `clientLoader.hydrate` is automatically treated as `true` since there is no server data to SSR with. Therefore, we always need to run the `clientLoader` on hydration before rendering the route component.</docs-info>
 
@@ -78,7 +78,7 @@ This function receives the same [`request`][loader-request] argument as a [`load
 
 ### `serverLoader`
 
-`serverLoader` is an asynchronous function to get the data from the server `loader` for this route. On client-side navigations, this will make a [fetch][fetch] call to the Remix server loader. If you opt-into running your `clientLoader` on hydration, then this function will return you the data that was already loaded on the server (via `Promise.resolve`).
+`serverLoader` is an asynchronous function to get the data from the server `loader` for this route. On client-side navigations, this will make a [fetch][fetch] call to the Remix server `loader`. If you opt-into running your `clientLoader` on hydration, then this function will return you the data that was already loaded on the server (via `Promise.resolve`).
 
 See also: