update jp copy

Author: swibi-ttd

i18n/ja/docusaurus-plugin-content-docs/current/ref-info/operator-private-network-requirements.md

@@ -1,7 +1,7 @@
 ---
-title: Private Operator network and firewall requirements
-sidebar_label: Private Operator network and firewall requirements
-pagination_label: Private Operator network and firewall requirements
+title: Private Operator network egress
+sidebar_label: Private Operator network egress
+pagination_label: Private Operator network egress
 description: Outbound network destinations a Private Operator must reach, for configuring egress firewall allowlists.
 hide_table_of_contents: false
 sidebar_position: 16
@@ -10,7 +10,7 @@ displayed_sidebar: docs
 
 import Link from '@docusaurus/Link';
 
-# Private Operator network and firewall requirements
+# Private Operator network egress
 
 A <Link href="../ref-info/glossary-uid#gl-private-operator">Private Operator</Link> connects to the UID2 <Link href="../ref-info/glossary-uid#gl-core-service">Core</Link> and <Link href="../ref-info/glossary-uid#gl-opt-out-service">Opt-Out</Link> services, and downloads data files directly from AWS S3 using URLs that the Core service provides. For details, see [Private Operator workflow](../guides/integration-options-private-operator.md#private-operator-workflow).