Update readme.md

readme.md

@@ -8,13 +8,17 @@ This is experimental and currently only supported in Svelte and React.
 
 This fork introduces the `<Frame>` component. This component is used to encapsulate an Inertia page within another Inertia page. This is useful for creating modal dialogs, wizards, search sidebars, popovers, etc.
 
-By default, hyperlinks and form submissions will load the response within the frame that contains the link or the form. To load the response in a different frame, add a `data-target` attribute. To load the response in the top (main) frame, use the `data=target="_top"` attribute.
+By default, hyperlinks and form submissions will render the response within the frame that contains the link or the form. To change the frame in which an Inertia response is rendered, do one of the following:
 
-You can overwrite the targeted frame in the server-side response by sending an 'X-Inertia-Frame' header.
+- Add a `data-target="frame-id"` attribute to an `a` tag.
+- Pass a  `{target: frameId}` to `router.visit()` or `form.submit()`
+- Specify the frame ID in an `X-Inertia-Frame` header from the server.
+
+To target the top (main) frame, use `_top` as the frame ID.
 
 Navigation within frames does not create new history entries. To enable this, a more substantial rewrite of the Inertia router would be required.
 
-### Installation
+### Try locally
 
 Clone this repo, [build it](https://github.com/inertiajs/inertia/blob/master/.github/CONTRIBUTING.md#packages), and in your `package.json`, link it like this: