Merge pull request #376 from benholmen/master

Edit spelling in docs

resources/js/Pages/deferred-props.jsx

@@ -21,7 +21,7 @@ export default function () {
       </P>
       <H2>Server side</H2>
       <P>
-        To defer a prop, you can use the <Code>defer</Code> method when returning your response. This method recieves a
+        To defer a prop, you can use the <Code>defer</Code> method when returning your response. This method receives a
         callback that returns the prop data. The callback will be executed in a separate request after the initial page
         render.
       </P>

resources/js/Pages/history-encryption.jsx

@@ -16,8 +16,8 @@ export default function () {
     <>
       <H1>History encryption</H1>
       <P>
-        Imagine a sceniario where your user is authenticated, browses priveleged information on your site, then logs
-        out. If they press the back button, they can still see the priveleged information that is stored in the window's
+        Imagine a scenario where your user is authenticated, browses privileged information on your site, then logs
+        out. If they press the back button, they can still see the privileged information that is stored in the window's
         history state. This is a security risk. To prevent this, Inertia.js provides a history encryption feature.
       </P>
       <H2>How it works</H2>

resources/js/Pages/routing.jsx

@@ -73,7 +73,7 @@ export default function () {
         ]}
       />
       <P>
-        However, when using Laravel, the <A href="https://github.com/tightenco/ziggy">Ziggy</A> library can make your
+        However, when using Laravel, the <A href="https://github.com/tighten/ziggy">Ziggy</A> library can make your
         named, server-side routes available to you via a global <Code>route()</Code> function. In fact, if you are
         developing an application using one of Laravel's{' '}
         <A href="https://laravel.com/docs/starter-kits">starter kits</A>, Ziggy is already configured for you.

resources/js/Pages/upgrade-guide.jsx

@@ -134,7 +134,7 @@ export default function () {
       <H3>Partial reloads are now async</H3>
       <P>
         Previously partial reloads in Inertia were synchronous, just like all Inertia requests. In v2.0, partial reloads
-        are now asynchronous. Generally this is desireable, but if you were relying on these requests being synchronous,
+        are now asynchronous. Generally this is desirable, but if you were relying on these requests being synchronous,
         you may need to adjust your code.
       </P>
     </>