diff --git a/content/en/faq/setup/k8s-auto-detect-inbound-ports.md b/content/en/faq/setup/k8s-auto-detect-inbound-ports.md
deleted file mode 100644
index f226797bad..0000000000
--- a/content/en/faq/setup/k8s-auto-detect-inbound-ports.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Kubernetes - How can I enable Istio sidecar to actively capture the inbound traffic on port list instead of using the automatical inbound port detection?
-weight: 20
----
-
-You can restore the white list capture ports model by overriding pod annotation `traffic.sidecar.istio.io/includeInboundPorts` to port list. Contrarily, to bypass the interception on certain ports, you can add pod annotation `traffic.sidecar.istio.io/excludeOutboundPorts` with bypass port list.
diff --git a/content/en/faq/traffic-management/controlling-inbound-ports.md b/content/en/faq/traffic-management/controlling-inbound-ports.md
new file mode 100644
index 0000000000..11d3046528
--- /dev/null
+++ b/content/en/faq/traffic-management/controlling-inbound-ports.md
@@ -0,0 +1,9 @@
+---
+title: On what ports does a sidecar proxy capture inbound traffic?
+weight: 20
+---
+
+Istio captures inbound traffic on all ports by default.
+You can override this behavior using the `traffic.sidecar.istio.io/includeInboundPorts` pod annotation
+to specify an explicit list of ports to capture, or using `traffic.sidecar.istio.io/excludeOutboundPorts`
+to specify a list of ports to bypass.