diff --git a/src/content/app-architecture/case-study/index.md b/src/content/app-architecture/case-study/index.md
index d54a7262d4..4b27f04b57 100644
--- a/src/content/app-architecture/case-study/index.md
+++ b/src/content/app-architecture/case-study/index.md
@@ -83,7 +83,7 @@ There are two popular means of organizing code:
 
 1. By feature - The classes needed for each feature are grouped together. For
    example, you might have an `auth` directory, which would contain files
-   like `auth_viewmodel.dart`, `login_usecase.dart`, `logout_usecase.dart,
+   like `auth_viewmodel.dart`, `login_usecase.dart`, `logout_usecase.dart`,
    `login_screen.dart`, `logout_button.dart`, etc.
 2. By type - Each "type" of architecture is grouped together.
    For example, you might have directories such as
diff --git a/src/content/app-architecture/case-study/ui-layer.md b/src/content/app-architecture/case-study/ui-layer.md
index 59986a4f14..900fb97663 100644
--- a/src/content/app-architecture/case-study/ui-layer.md
+++ b/src/content/app-architecture/case-study/ui-layer.md
@@ -578,7 +578,7 @@ the view wants to render. This gets at *why* the Compass app uses `Commands`.
 In the view's `Widget.build` method,
 the command is used to conditionally render different widgets.
 
-```dart title=home_viewmodel.dart
+```dart title=home_screen.dart
 // ...
 child: ListenableBuilder(
   listenable: [!viewModel.load!],
diff --git a/src/content/cookbook/navigation/set-up-app-links.md b/src/content/cookbook/navigation/set-up-app-links.md
index d91625a869..af5e80210e 100644
--- a/src/content/cookbook/navigation/set-up-app-links.md
+++ b/src/content/cookbook/navigation/set-up-app-links.md
@@ -96,17 +96,29 @@ It provides a simple API to handle complex routing scenarios.
         <data android:scheme="https" />
     </intent-filter>
     ```
-   
+
+    :::version-note
+    If you use a Flutter version earlier than 3.27,
+    you need to manually opt in to deep linking by
+    adding the following metadata tag to `<activity>`:
+
+    ```xml
+    <meta-data android:name="flutter_deeplinking_enabled" android:value="true" />
+    ```
+    :::
+
     :::note
     If you use a third-party plugin to handle deep links,
-    such as [app_links][], 
+    such as [app_links][],
     Flutter's default deeplink handler will
-    break these plugins. 
-    
+    break these plugins.
+
     To opt out of using Flutter's default deep link handler,
-     add the following metadata tag:
-    ```<meta-data android:name="flutter_deeplinking_enabled" android:value="false" />```
-    to opt out of Flutter's default deeplink handler 
+    add the following metadata tag to `<activity>`:
+
+    ```xml
+    <meta-data android:name="flutter_deeplinking_enabled" android:value="false" />
+    ```
     :::
 
 ## 3. Hosting assetlinks.json file
diff --git a/src/content/cookbook/navigation/set-up-universal-links.md b/src/content/cookbook/navigation/set-up-universal-links.md
index 604f1ffa0e..87fe90fb70 100644
--- a/src/content/cookbook/navigation/set-up-universal-links.md
+++ b/src/content/cookbook/navigation/set-up-universal-links.md
@@ -82,15 +82,21 @@ It provides a simple API to handle complex routing scenarios.
 1. Open the `ios/Runner.xcworkspace` file inside the
    Flutter project's `ios` folder.
 
-  :::note
-  If you are using third-party plugins to handle deep links, 
-  such as [app_links][],
-  Flutter's default deeplink handler will
-  break these plugins. 
-
-  If you use a third-party plugin,
-  add the key and value pair `FlutterDeepLinkingEnabled` and `NO` to info.Plist.
-  :::
+   :::version-note
+   If you use a Flutter version earlier than 3.27,
+   you need to manually opt in to deep linking by adding the
+   key and value pair `FlutterDeepLinkingEnabled` and `YES` to `info.Plist`.
+   :::
+
+   :::note
+   If you're using third-party plugins to handle deep links, 
+   such as [app_links][],
+   Flutter's default deeplink handler will
+   break these plugins.
+
+   If you use a third-party plugin, add the
+   key and value pair `FlutterDeepLinkingEnabled` and `NO` to `info.Plist`.
+   :::
 
 ### Add associated domains
 
diff --git a/src/content/platform-integration/web/renderers.md b/src/content/platform-integration/web/renderers.md
index 0ec54a1cd4..25f4b509b5 100644
--- a/src/content/platform-integration/web/renderers.md
+++ b/src/content/platform-integration/web/renderers.md
@@ -11,7 +11,7 @@ Flutter chooses the build mode when building the app,
 and determines which renderers are available at runtime.
 
 For a default build,
-Flutter chooses the`canvaskit` renderer at runtime.
+Flutter chooses the `canvaskit` renderer at runtime.
 For a WebAssembly build,
 Flutter chooses the `skwasm` renderer at runtime,
 and falls back to `canvaskit` if the browser doesn't support `skwasm`.