Fix swapped registration links, drop Talk details button

Registration URLs were swapped between the two webinars. Also removes
the separate "Talk details" external link in favor of pulling the
fuller abstract from each talk's Percona Live page directly into the
webinar's own description, so there's one page to read instead of two.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: Mazizova

content/community/webinars/beyond-the-proxy-proxysql-ecosystem/index.md

@@ -3,8 +3,7 @@ title: "Beyond the Proxy: The Expanding ProxySQL Ecosystem"
 description: "ProxySQL has grown well beyond a proxy. René and Alkin cover MySQL and PostgreSQL support, the expansion toward DuckDB, deeper cloud integration, and where Orchestrator and dbdeployer fit in — tied together through real operational problems instead of a feature list."
 date: 2026-11-03
 time_display: "10:00 AM ET · 16:00 CET"
-talk_url: "https://perconalive.com/2026-amsterdam/talks/beyond-the-proxy-the-expanding-proxysql-ecosystem/"
-registration_url: "https://us06web.zoom.us/webinar/register/WN_AYk4qjMBTU2ofrY_hkpXvQ"
+registration_url: "https://us06web.zoom.us/webinar/register/WN_X82k7xu-STmLLTln6NjTHw"
 images:
   - banner.jpg
 speakers:
@@ -17,11 +16,13 @@ speakers:
     linkedin: "https://www.linkedin.com/in/askdba/"
 ---
 
-ProxySQL has grown well beyond a proxy. René and Alkin cover:
+Modern database infrastructure increasingly spans multiple database engines, deployment models, and operational environments. The ProxySQL ecosystem is evolving to address that broader landscape — bringing together database connectivity, traffic management, high availability, testing, and production operations.
+
+René and Alkin walk through the current state and future direction of the ecosystem:
 
 - MySQL and PostgreSQL support
 - the expansion toward DuckDB
-- deeper cloud integration
-- where Orchestrator and dbdeployer fit in
+- deeper integration with cloud platforms and managed environments
+- how related projects like Orchestrator and dbdeployer complement it across the database lifecycle
 
-They tie it all together through real operational problems instead of a feature list.
+Rather than a catalogue of products and features, the session connects these pieces through real operational challenges — you'll leave with a clear picture of how they fit together, which problems each one addresses, and how ProxySQL is evolving beyond the traditional boundaries of a database proxy.

content/community/webinars/mysql-time-travel-row-level-recovery/index.md

@@ -3,8 +3,7 @@ title: "MySQL Time Travel: Practical Row-Level Recovery With Open Source Tools"
 description: "A bad UPDATE hit a handful of rows. Do you really need to restore a full backup and replay binlogs? In a mostly live demo, Daniel shows how to see exactly which rows changed, query any table as it looked at a past moment, and generate the exact statements to undo the damage."
 date: 2026-10-15
 time_display: "10:00 AM ET · 16:00 CEST"
-talk_url: "https://perconalive.com/2026-amsterdam/talks/mysql-time-travel-practical-row-level-recovery-with-open-source-tools/"
-registration_url: "https://us06web.zoom.us/webinar/register/WN_X82k7xu-STmLLTln6NjTHw"
+registration_url: "https://us06web.zoom.us/webinar/register/WN_AYk4qjMBTU2ofrY_hkpXvQ"
 images:
   - banner.jpg
 speakers:
@@ -14,10 +13,17 @@ speakers:
     linkedin: "https://www.linkedin.com/in/danielmauricioguzman/"
 ---
 
-A bad `UPDATE` hit a handful of rows. Do you really need to restore a full backup and replay binlogs? In a mostly live demo, Daniel shows how to:
+Recovering from a bad `UPDATE` or `DELETE` in MySQL is disproportionately expensive: restore a backup and replay binlogs, or hand-parse `mysqlbinlog` output and reconstruct the reversal manually. Both take hours for incidents that touched a handful of rows.
 
-- see exactly which rows changed and when
-- query any table as it looked at a past moment, using plain SQL
-- generate the exact statements to undo the damage, including FK cascades that manual binlog parsing tends to miss
+This session shows a faster workflow using [dbtrail](https://dbtrail.com), an open source (Apache 2.0) tool that captures every row change from the binlog and makes it queryable — in a mostly live demo, on a real schema, with a real mistake and a real recovery.
 
-The same setup works on-prem and on RDS or Aurora.
+Step by step, Daniel shows how to:
+
+- identify which rows changed and when
+- inspect full before-and-after images of each change
+- query any table **as of** a past timestamp, using plain SQL
+- generate the exact reversal statements for the incident — including changes propagated through FK cascades, which manual binlog parsing usually gets wrong
+
+He'll also cover verifying that the captured history matches the source — a check worth running before trusting any of it for recovery.
+
+Capture works over the replication protocol, so the same setup runs on-premises and on RDS or Aurora, where binlog files on disk aren't accessible. Deployment is Docker Compose, and everything shown is reproducible on a test instance.

layouts/community/webinars/single.html

@@ -61,7 +61,6 @@ <h1>{{ .Title }}</h1>
 
     <div class="about-cta-row">
       {{ with $primaryURL }}<a href="{{ . }}" class="about-btn about-btn--primary" target="_blank" rel="noopener">{{ $primaryLabel }}</a>{{ end }}
-      {{ with .Params.talk_url }}<a href="{{ . }}" class="about-btn about-btn--secondary" target="_blank" rel="noopener">Talk details</a>{{ end }}
     </div>
   </header>