No longer mark DbgEng TTD as beta

core/adapters/dbgengttdadapter.cpp

@@ -261,7 +261,7 @@ bool DbgEngTTDAdapter::Quit()
 }
 
 
-DbgEngTTDAdapterType::DbgEngTTDAdapterType() : DebugAdapterType("DBGENG_TTD (BETA)") {}
+DbgEngTTDAdapterType::DbgEngTTDAdapterType() : DebugAdapterType("DBGENG_TTD") {}
 
 
 DebugAdapter* DbgEngTTDAdapterType::Create(BinaryNinja::BinaryView* data)

docs/guide/dbgeng-ttd.md

@@ -1,4 +1,4 @@
-# Time Travel Debugging (beta)
+# Time Travel Debugging
 
 Time travel debugging (TTD) allows you to record an execution trace of a program or system and replay it back and forth.
 It can speed up the process of reverse engineering/vulnerability research, and deal with certain tasks that are not easy to handle in regular forward debugging.
@@ -64,7 +64,7 @@ So you will need to copy the entire WinDbg installation folder to a place that B
 
 - Open the .exe or .dll file in Binary Ninja
 - Click `Debugger` -> `Debug Adapter Settings`
-- For `Adapter Type`, select `DBGENG_TTD (BETA)`
+- For `Adapter Type`, select `DBGENG_TTD`
 - For `Executable Path`, select the trace file recorded by WinDbg in the previous step
     - E.g., `C:/Users/xushe/Documents/helloworld01.run`
 - Click `Accept`

docs/guide/index.md

@@ -326,9 +326,9 @@ This is especially helpful to quickly navigate to the stack variables since they
 
 See [Remote Debugging Guide](remote-debugging.md)
 
-### Time-travel Debugging (beta)
+### Time-travel Debugging
 
-See [Time Travel Debugging (beta) Guide](dbgeng-ttd.md)
+See [Time Travel Debugging Guide](dbgeng-ttd.md)
 
 ### Windows Kernel Debugging