deploy: a27c4b6

hotwired · Dec 18, 2024 · b211477 · b211477
1 parent 673a990
commit b211477
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/handbook/native.html b/handbook/native.html
@@ -6,7 +6,7 @@
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
   <title>Turbo Handbook</title>
-  <meta name="description" content="Turbo Native lets your majestic monolith form the center of your native iOS and Android apps, with seamless transitions between web and native sections.">
+  <meta name="description" content="Hotwire Native lets your majestic monolith form the center of your native iOS and Android apps, with seamless transitions between web and native sections.">
   <link rel="canonical" href="https://turbo.hotwired.dev/handbook/native">
 
   <link rel="alternate icon" type="image/png" sizes="32x32" href="/assets/favicon-32x32.png">
@@ -151,9 +151,9 @@
   <section id="content" class="docs__content grid__custom-item">
 
     <h1>Go Native on iOS &amp; Android</h1>
-<p>Turbo Native for iOS provides the tooling to wrap your Turbo-enabled web app in a native iOS shell. It manages a single WKWebView instance across multiple view controllers, giving you native navigation UI with all the client-side performance benefits of Turbo. See <a href="https://github.com/hotwired/turbo-ios">Turbo Native: iOS</a> for more details.</p>
-<p>Turbo Native for Android provides the same kind of tooling, managing a single WebView instance across multiple Fragment destinations. See <a href="https://github.com/hotwired/turbo-android">Turbo Native: Android</a> for more details.</p>
-<p>The best way to see what’s possible with the native adapters is to setup the demo native application. We have one <a href="https://github.com/hotwired/turbo-ios/blob/main/Demo/README.md">for iOS</a> and <a href="https://github.com/hotwired/turbo-android/blob/main/demo/README.md">for Android</a>. You can open the code in your native environments and follow along to explore all the features.</p>
+<p>Hotwire Native for iOS provides the tooling to wrap your Turbo-enabled web app in a native iOS shell. It manages a single WKWebView instance across multiple view controllers, giving you native navigation UI with all the client-side performance benefits of Turbo. See <a href="https://github.com/hotwired/hotwire-native-ios/">Hotwire Native: iOS</a> for more details.</p>
+<p>Hotwire Native for Android provides the same kind of tooling, managing a single WebView instance across multiple Fragment destinations. See <a href="https://github.com/hotwired/hotwire-native-android/">Hotwire Native: Android</a> for more details.</p>
+<p>The best way to see what’s possible with the native adapters is to setup the demo native application. We have one <a href="https://native.hotwired.dev/ios/getting-started">for iOS</a> and <a href="https://native.hotwired.dev/android/getting-started">for Android</a>. You can open the code in your native environments and follow along to explore all the features.</p>
 <p><a class="button" href="/handbook/building">Next: Building Your Turbo Application</a></p></section>
 
   <footer class="docs__footer grid__item grid__item--start-4 grid__item--span-8">

diff --git a/index.html b/index.html
@@ -141,7 +141,7 @@ <h1 class="landing-intro__text grid__item grid__item--start-2 grid__item--span-1
 </div>
 
 <p class="landing-version">
-  <span>Current version: <a href="https://github.com/hotwired/turbo/releases/tag/v8.0.10">8.0.10</a> &mdash; released Sep 18, 2024</span>
+  <span>Current version: <a href="https://github.com/hotwired/turbo/releases/tag/v8.0.11">8.0.11</a> &mdash; released Oct 15, 2024</span>
 </p>
 
 <section class="landing-summary">