fix(DOC-1959): correct election_timeout_ms type/default; exclude raft_election_timeout_ms

modules/get-started/pages/architecture.adoc

@@ -39,7 +39,7 @@ As long as the leader and a majority of the replicas are stable, Redpanda can to
 
 == Partition leadership elections
 
-https://raft.github.io/[Raft^] uses a heartbeat mechanism to maintain leader authority and to trigger leader elections. The partition leader sends a periodic heartbeat to all followers to assert its leadership in the current term (default = 150 milliseconds). A term is an arbitrary period of time that starts when a leader election is triggered. If a follower does not receive a heartbeat over a period of time (default = 1.5 seconds), then it triggers an election to choose a new partition leader. The follower increments its term and votes for itself to be the leader for that term. It then sends a vote request to the other nodes and waits for one of the following scenarios:
+https://raft.github.io/[Raft^] uses a heartbeat mechanism to maintain leader authority and to trigger leader elections. The partition leader sends a heartbeat to all followers every 150 milliseconds to assert its leadership in the current term (an election cycle). If a follower does not receive a heartbeat within the election timeout, it triggers an election to choose a new partition leader. Configure the election timeout with the xref:reference:properties/cluster-properties.adoc#election_timeout_ms[`election_timeout_ms`] cluster property (default: 1500 milliseconds). The follower increments its term and votes for itself to be the leader for that term. It then sends a vote request to the other nodes and waits for one of the following scenarios:
 
 * It receives a majority of votes and becomes the leader. Raft guarantees that at most one candidate can be elected the leader for a given term.
 * Another follower establishes itself as the leader. While waiting for votes, the candidate may receive communication from another node in the group claiming to be the leader. The candidate only accepts the claim if its term is greater than or equal to the candidate's term; otherwise, the communication is rejected and the candidate continues to wait for votes.

modules/get-started/pages/licensing/overview.adoc

@@ -88,7 +88,7 @@ IMPORTANT: To avoid startup issues with Redpanda Console when a trial or Enterpr
 - **Redpanda Connect**: To evaluate enterprise features in Redpanda Connect, you must xref:redpanda-connect:get-started:licensing.adoc#apply-a-license-key-to-redpanda-connect[apply a trial license key]. After the 30-day evaluation period, you are blocked from using enterprise connectors unless you https://www.redpanda.com/upgrade[upgrade to an Enterprise Edition license^].
 
 [[self-managed]]
-=== Redpanda enterprise features
+=== Redpanda Enterprise Edition features
 
 The following table lists the enterprise features for Redpanda and how Redpanda behaves upon license expiration when each enterprise feature is enabled.
 
@@ -136,7 +136,7 @@ Continuous Intra-Broker Partition Balancing is enabled by default for all new cl
 | Provides secure Kerberos-based authentication.
 | No change.
 
-| xref:manage:security/authentication.adoc#kerberos[Leader Pinning]
+| xref:develop:produce-data/leader-pinning.adoc[Leader Pinning]
 | Specifies the set of availability zones where the leaders of partitions of a given topic should be located.
 | Leader Pinning is disabled on all topics.
 
@@ -164,6 +164,10 @@ Continuous Intra-Broker Partition Balancing is enabled by default for all new cl
 | Provides enterprise-grade disaster recovery through asynchronous, offset-preserving replication between distinct Redpanda clusters for cross-region data protection.
 | New shadow links cannot be created. Existing shadow links continue operating and can be updated.
 
+| Topic Deletion Control (`delete_topic_enable`)
+| When set to `false`, prevents all users, including superusers, from deleting topics through the Kafka DeleteTopics API. Use this as a cluster-wide safety setting to prevent accidental topic deletion.
+| Topic deletion is re-enabled (reverts to `true`).
+
 | xref:manage:topic-recovery.adoc[Topic Recovery]
 | Allows restoring a single topic from Tiered Storage using remote recovery properties.
 | You cannot create topics with the `redpanda.remote.recovery=true` property or perform topic recovery operations. To proceed, add a valid license to the target cluster. Without a valid license, topic recovery is blocked.