diff --git a/_source/handbook/01_introduction.md b/_source/handbook/01_introduction.md index cd2b786..28b01b5 100644 --- a/_source/handbook/01_introduction.md +++ b/_source/handbook/01_introduction.md @@ -22,7 +22,7 @@ This happens by intercepting all clicks on `` links to the same domain. Same deal with forms. Their submissions are turned into `fetch` requests from which Turbo Drive will follow the redirect and render the HTML response. -During rendering, Turbo Drive replaces the current `` element outright and merges the contents of the `` element. The JavaScript window and document objects, and the `` element, persist from one rendering to the next. +During rendering, Turbo Drive replaces the contents of the `` element and merges the contents of the `` element. The JavaScript window and document objects, and the `` element, persist from one rendering to the next. While it's possible to interact directly with Turbo Drive to control how visits happen or hook into the lifecycle of the request, the majority of the time this is a drop-in replacement where the speed is free just by adopting a few conventions. diff --git a/_source/handbook/03_page_refreshes.md b/_source/handbook/03_page_refreshes.md index 74daa71..fc515df 100644 --- a/_source/handbook/03_page_refreshes.md +++ b/_source/handbook/03_page_refreshes.md @@ -22,7 +22,7 @@ You can configure how Turbo handles page refresh with a `