diff --git a/_features/autofill.md b/_features/autofill.md
index 42f22c0..09a43ed 100644
--- a/_features/autofill.md
+++ b/_features/autofill.md
@@ -27,7 +27,7 @@ stats: {
     },
     webview2: {
         windows: {
-            "*": "u"
+            "*": "y"
         }
     }
 }
@@ -35,7 +35,7 @@ stats: {
 
 ## WebView2
 
-TODO: Complete me!
+Will autofill any fields that Microsoft Edge will, such as names, street, email addresses, phone numbers, passwords, etc. Developers can control this in their application using the `CoreWebView2Settings.IsGeneralAutofillEnabled` and `CoreWebView2Settings.IsPasswordAutosaveEnabled` properties.
 
 ## WKWebView
 
diff --git a/_features/cookies.md b/_features/cookies.md
index a5a551c..d4f920b 100644
--- a/_features/cookies.md
+++ b/_features/cookies.md
@@ -27,14 +27,14 @@ stats: {
     },
     webview2: {
         windows: {
-            "*": "u"
+            "*": "y"
         }
     }
 }
 ---
 ## WebView2
 
-TODO: Complete me!
+Applications can access, modify, delete, or copy the cookies of their WebView2 instance via the `CoreWebView2.CookieManager` property. By default, WebView2 has [Tracking Prevention](https://learn.microsoft.com/microsoft-edge/web-platform/tracking-prevention) set to "Balanced" by default and can be modified using the `CoreWebView2EnvironmentOptions.EnableTrackingPrevention` property.
 
 ## WKWebView
 
diff --git a/_features/localhost.md b/_features/localhost.md
index 98a7d7b..5404daf 100644
--- a/_features/localhost.md
+++ b/_features/localhost.md
@@ -31,14 +31,14 @@ stats: {
     },
     webview2: {
         windows: {
-            "*": "u"
+            "*": "y"
         }
     }
 }
 ---
 ## WebView2
 
-TODO: Complete me!
+WebView2 has a variety of ways to work with local content - intercepting web resources as they're requested, mapping a hostname to a folder on the user's filesystem, or registering a custom URL scheme. You can find details on all of these in WebView2's documentation for [working with local content in WebView2 apps](https://learn.microsoft.com/microsoft-edge/webview2/concepts/working-with-local-content).
 
 ## WKWebView
 
diff --git a/_features/updates_cadence.md b/_features/updates_cadence.md
index 456fb77..1fbb8a5 100644
--- a/_features/updates_cadence.md
+++ b/_features/updates_cadence.md
@@ -27,14 +27,16 @@ stats: {
     },
     webview2: {
         windows: {
-            "*": "u"
+            "*": "y"
         }
     }
 }
 ---
 ## WebView2
 
-TODO: Complete me!
+WebView2 has two options for updating - Evergreen Runtime or Fixed Runtime. Evergreen runtime is automatically included in recent versions of Windows, and developers can also include a small installer alongside theirs to be confident it's available. This version is updated automatically with major releases every four weeks, roughly following Chromium's releases. When using a fixed runtime, the application developer distributes the WebView2 components with their app and chooses when to update to a newer version. Details on the type of runtimes can be found [here](https://learn.microsoft.com/microsoft-edge/webview2/concepts/distribution), and details on evergreen updates can be found [here](https://learn.microsoft.com/deployedge/microsoft-edge-relnote-stable-channel).
+
+SDK updates are also every four weeks, and their details are [here](https://learn.microsoft.com/microsoft-edge/webview2/release-notes/about)
 
 ## WKWebView