diff --git a/contributors.yml b/contributors.yml index c11fb3b3030..55f486972af 100644 --- a/contributors.yml +++ b/contributors.yml @@ -529,6 +529,7 @@ - oott123 - orballo - oscarnewman +- outofgamut - ovi-ispas - pacexy - pandaiolo diff --git a/docs/discussion/introduction.md b/docs/discussion/introduction.md index 68c30f145d8..e36c98e43d7 100644 --- a/docs/discussion/introduction.md +++ b/docs/discussion/introduction.md @@ -150,7 +150,7 @@ Once Remix has served the document to the browser, it "hydrates" the page with t When the user clicks a link, instead of making a round trip to the server for the entire document and all the assets, Remix simply fetches the data for the next page and updates the UI. -Additionally, when users submit a `
` to update data, instead of doing a normal HTML document request, the browser runtime will make a fetch to the server instead and automatically revalidate all data on the page and updating it with React. +Additionally, when users submit a `` to update data, instead of doing a normal HTML document request, the browser runtime will make a fetch to the server instead and automatically revalidate all data on the page and update it with React. This has many performance benefits over making a full-document request: