Update README to point to 0.12.0 branch

README.md

@@ -26,28 +26,22 @@ that it proved to be:
 
 Exactly the goals I set out to achieve!
 
-## <mark>**Zap depends on the latest stable release of Zig (0.11)**</mark>
 
 ## Most FAQ:
 
 - Q: **Zap doesn't build with Zig master?**
-- A: <mark>**Zap depends on the latest stable release of Zig**, which is **ZIG
-  V0.11**</mark> at the moment. Contributers provide forks with v0.12/master
-  branches which I may integrate soon-ish.
-    - A2: Going "stable" is a deliberate decision. Zap is designed to be
-      depended on by professional, production-grade servers, not just toy
-      projects or Zig/Zap enthusiasts. Having zap not break with frequent
-      changes of zig master, is a feature. We experienced the catch-up game when
-      Zig 0.11 was in development and decided that it might be a big turn-off,
-      especially for professional projects.
-    - A3: We're going to add a `zig-master` branch soon. (Probably early 2024).
+- A: See the 0.12.0 branch. An example on how to use it is
+  [here](https://github.com/zigzap/hello-0.12.0). Please note that the 0.12.0
+  branch is not the official master branch of ZAP. Yet. Until zig 0.12.0 is
+  released.
 - Q: **Does ZAP work on Windows?**
 - A: No. This is due to the underlying facil.io C library. Future versions of
   facil.io might support Windows but there is no timeline yet. Your best options
   on Windows are WSL2 or a docker container.
 - Q: **Does ZAP support TLS / HTTPS?**
 - A: Yes, ZAP supports using the system's openssl. See the
-  [https](./examples/https/https.zig) example.
+  [https](./examples/https/https.zig) example and make sure to build with
+  `-Dopenssl=true`.
 
 ## Here's what works