update format

Author: bluebill1049

next-env.d.ts

@@ -1,5 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
+/// <reference path="./.next/types/routes.d.ts" />
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/pages/api-reference/config/typescript for more information.

src/content/docs/useform.mdx

@@ -287,7 +287,6 @@ By default, an input value will be retained when input is removed. However, you
 - By default, `shouldUnregister: false` means unmounted fields are **not validated** by built-in validation.
 - By setting `shouldUnregister` to true at `useForm` level, `defaultValues` will **not** be merged against submission result.
 - Setting `shouldUnregister: true` makes your form behave more closely to native forms.
-
   - Form values are stored within the inputs themselves.
   - Unmounting an input removes its value.
   - Hidden inputs should use the `hidden` attribute for storing hidden data.

src/content/docs/useform/getfieldstate.mdx

@@ -37,7 +37,6 @@ This method is introduced in react-hook-form ([v7.25.0](https://github.com/react
   getFieldState("non-existent-name") // ❌ will return state as false and error as undefined
   ```
 - `getFieldState` works by subscribing to the form state update, and you can subscribe to the formState in the following ways:
-
   - You can subscribe at the `useForm`, `useFormContext` or `useFormState`. This is will establish the form state subscription and `getFieldState` second argument will no longer be required.
 
     ```javascript

src/content/docs/useform/setvalue.mdx

@@ -48,7 +48,6 @@ This function allows you to dynamically set the value of a <strong>registered</s
   ```
 
 - Only the following conditions will trigger a re-render:
-
   - When an error is triggered or corrected by a value update.
   - When `setValue` cause state update, such as dirty and touched.