From 39e67a90d630bf8cbd35fad60ecf90470327014b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Susa=20T=C3=BCnker?=
 <74345218+sujaya-sys@users.noreply.github.com>
Date: Wed, 26 Feb 2025 09:01:59 +0100
Subject: [PATCH] Removed TCP check beta note (#1219)

---
 site/content/docs/tcp-checks/_index.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/site/content/docs/tcp-checks/_index.md b/site/content/docs/tcp-checks/_index.md
index d0dac293d..5f0e2fbd2 100644
--- a/site/content/docs/tcp-checks/_index.md
+++ b/site/content/docs/tcp-checks/_index.md
@@ -10,8 +10,6 @@ slug: /
 
 ---
 
-> This feature is currently in beta. We’d love to hear your feedback—connect with us via the [Checkly community Slack](https://www.checklyhq.com/slack) or reach out to our [support team](mailto:support@checklyhq.com).
-
 ## Overview
 
 A TCP check establishes a connection to a specified hostname or IP address and port to verify responsiveness. These checks are ideal for monitoring non-HTTP services critical to your infrastructure. Here are a few example use cases: