diff --git a/src/content/docs/service-architecture-intelligence/catalogs/applications-catalog.mdx b/src/content/docs/service-architecture-intelligence/catalogs/applications-catalog.mdx
index 34332e2a8a0..33b0defdd79 100644
--- a/src/content/docs/service-architecture-intelligence/catalogs/applications-catalog.mdx
+++ b/src/content/docs/service-architecture-intelligence/catalogs/applications-catalog.mdx
@@ -9,14 +9,14 @@ tags:
 freshnessValidatedDate: never
 ---
 
-<Callout title="Preview">
-    We're still working on this feature, but we'd love for you to try it out!
 
-    This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
+Applications catalog offers a single pane view to enhance the observability and management of entities in your organization. The unified view of Services - APM, Services - OpenTelemetry, Browser, and Mobile entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams.
 
+<Callout variant="important">
 
-Applications catalog offers a single pane view to enhance the observability and management of entities in your organization. The unified view of Services - APM, Services - OpenTelemetry, Browser, and Mobile entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams.
+    The Applications catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).
+    
+</Callout>
 
 
 ### Supported entities [#supported-entities]
@@ -79,8 +79,8 @@ The <DNT>Application Catalog</DNT> page has multiple columns to displays various
             <td>The team responsible for the entity. Click on the team's name to go to the corresponding team's hub page to view more information of team's managing the entity. Hover the mouse to the <DNT>Team</DNT> link to view additional details in the pop-up dialog box. If a Team is not assigned to an entity, click the <DNT>Assign Team</DNT> button and select the responsible team from the displayed list. For more information, refer [Teams](/docs/service-architecture-intelligence/teams/teams). </td>
         </tr>
         <tr>
-            <td><DNT>Issues</DNT></td>
-            <td>The number of active issues created in the <DNT>past 24 hours</DNT>. Hover the mouse to the cell to view a brief overview on those entities' issues. Click the number to view the details. Hover the mouse to the <DNT>Issues</DNT> link to view additional details in the pop-up dialog box. You can also click the links in the pop-up dialog box to open the Alerts. For more information, refer [Alerts](/docs/alerts/overview/) and [Issues](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td>
+            <td><DNT>Alerts</DNT></td>
+            <td>The number of active alerts created in the <DNT>past 24 hours</DNT>. Hover the mouse to the cell to view a brief overview on those entities' alerts. Click the link in the pop-up dialog box to view additional details. For more information, refer [Alerts](/docs/alerts/overview/) and [Issues](/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td> 
         </tr>
         <tr>
             <td><DNT>Last Deploy</DNT></td>
diff --git a/src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx b/src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx
index 855b785f4c6..bff60463f1e 100644
--- a/src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx
+++ b/src/content/docs/service-architecture-intelligence/catalogs/catalogs.mdx
@@ -6,19 +6,13 @@ tag:
     - "Applications Catalog"
     - "Repositories Catalog"
     - "Infrastructure Catalog"
+    - "All in one Catalog"
+    - 'New Relic Catalogs'
 metaDescription: "Catalogs offer a single pane view to enhance the observability and management of software systems in your organization. The unified view of system entities facilitates well-informed decision-making, streamlined operations, and improved collaboration across teams."
 freshnessValidatedDate: never
 ---
 
 
-<Callout title="Preview">
-We're still working on this feature, but we'd love for you to try it out!
-
-This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
-
-
-
 New Relic Catalogs provides a single-pane view that enhances the observability and management of systems across your organization. By offering a unified perspective on entities, it empowers teams to make well-informed decisions, streamline operations, and collaborate more effectively.
 
 With Catalogs, you can quickly identify and focus on the most relevant information, ensuring easy access to what matters most. It serves as the single source of truth, enabling users to discover, manage, and optimize their systems with confidence.
@@ -151,3 +145,7 @@ To go back to the <DNT>Catalogs</DNT> view, click the <DNT>**Try it out**</DNT>
             alt="Catalog"
             src={CatalogHome}
     /> */}
+
+## Pricing [#pricing]
+
+The Catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).
\ No newline at end of file
diff --git a/src/content/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx b/src/content/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx
new file mode 100644
index 00000000000..95424ff1eec
--- /dev/null
+++ b/src/content/docs/service-architecture-intelligence/catalogs/infrastructure-catalog.mdx
@@ -0,0 +1,175 @@
+---
+title: "Infrastructure Catalog"
+metaDescription: "Learn how to use the Infrastructure Catalog to manage your infrastructure resources in New Relic."
+tag: 
+    - "Service Architecture Intelligence"
+    - "Catalogs"
+    - "Applications Catalog"
+    - "Repositories Catalog"
+    - "Infrastructure Catalog"
+    - "All in one Catalog"
+    - 'New Relic Catalogs'
+freshnessValidatedDate: never
+---
+
+
+The Infrastructure Catalog provides a complete inventory of all your infrastructure entities. Use it to manage resources, accelerate root cause analysis, and identify observability gaps. The catalog displays key information for each resource, including high-level details, ownership, configuration data, and its relationships with other resources, applications, and services.
+
+Data is populated automatically from New Relic infrastructure agents and cloud integrations.
+
+<Callout variant="important">
+
+    The Infrastructure catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).
+
+</Callout>
+
+## Key features [#key-features]
+
+* **Centralized resource view:** Gain a high-level, cross-account view of your infrastructure resources. Filter and group by attributes like resource category, entity type, region, environment, or team to improve organization and visibility.
+
+* **Application and service mapping:** See which applications and services are running on each compute resource to quickly assess impact and triage issues.
+
+* **Clear ownership and accountability:** Easily identify owners for both infrastructure components and their dependent applications or services. This clarifies accountability when infrastructure issues arise.
+
+* **Actionable resource insights:** Access insights into infrastructure activity—including health status, related incidents, scorecards, and more—to inform your resource optimization efforts.
+
+* **Detailed resource configuration:** Quickly access current configuration data for each resource, enabling faster debugging and reducing context switching.
+
+## Access the Infrastructure catalog [#access-infra-catalog]
+
+The Infrastructure catalog is available in the New Relic platform, providing a comprehensive view of your infrastructure resources. You can use it to manage your resources, accelerate root cause analysis, and identify observability gaps.
+
+**Prerequisites:**
+
+* Enable the Catalogs in your New Relic account. For more information, refer [Enable the Catalogs](https://docs.newrelic.com/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs).
+
+**To access the Infrastructure catalog inventory:**
+
+1. Log in to your New Relic platform.
+2. Go to the <DoNotTranslate>left navigation pane > Catalogs > Infrastructure catalog</DoNotTranslate>.
+
+    <img
+            title="Infrastructure catalogs"
+            alt="An infrastructure catalog view in New Relic"
+            src="/images/infracatalogs.webp"
+    />
+
+    The Infrastructure Catalog page displays multiple columns to present various information for an infra resource:
+
+<table>
+    <thead>
+        <tr>
+            <th>UI</th>
+            <th>Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>Name</td>
+            <td>
+                The name of the infrastructure entity.
+                <ul>
+                    <li>Click the entity name to open its Entity Overview page.</li>
+                    <li>Hover over the entity name to view additional details in a pop-up. You can also click links within this pop-up.</li>
+                </ul>
+            </td>
+        </tr>
+        <tr>
+            <td>Type</td>
+            <td>The type of the infrastructure resource. For example, `Host`, `KubernetesCluster`.</td>
+        </tr>
+        <tr>
+            <td>Category</td>
+            <td>
+                A high-level grouping of resources. Supported categories include:
+                <ul>
+                    <li>`AI + ML`</li>
+                    <li>`Analytics`</li>
+                    <li>`Compute`</li>
+                    <li>`Database`</li>
+                    <li>`Networking`</li>
+                    <li>`Other`</li>
+                    <li>`Queues/Streams/Events`</li>
+                    <li>`Security & Identity`</li>
+                    <li>`Storage`</li>
+                </ul>
+            </td>
+        </tr>
+        <tr>
+            <td>Cloud</td>
+            <td>The cloud provider for the entity. It can be `AWS`, `Azure`, `GCP`, or any other. For `Hosts` and `Containers`, the cloud provider is determined by checking the `cloudProvider` tag. For all other entity types, the cloud is automatically identified.</td>
+        </tr>
+        <tr>
+            <td>Score</td>
+            <td>The percentage of scorecard rules passed by the entity. This value helps you measure how entities are performing against best practices defined in the Scorecards capability. Hover over the score to view a summary. For more information, refer to [Scorecards](https://docs.newrelic.com/docs/service-architecture-intelligence/scorecards/getting-started/).</td>
+        </tr>
+        <tr>
+            <td>Team</td>
+            <td>
+                The team responsible for the entity.
+                <ul>
+                    <li>Click a team name to navigate to that team's page.</li>
+                    <li>Hover over a team name to view additional details.</li>
+                    <li>If a team is not assigned, click Assign Team and select the responsible team.</li>
+                </ul>
+                For more information, refer to [Teams](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/teams/).
+            </td>
+        </tr>
+        <tr>
+            <td>Services</td>
+            <td>The number of related services and applications running on the infrastructure resource. This data is derived from New Relic entity relationships to help you understand service-to-infrastructure dependencies. Hover over the number to see a list of related services. You can click links in the pop-up to navigate to those services.</td>
+        </tr>
+        <tr>
+            <td>Alerts</td>
+            <td>The number of active alerts impacting the entity within the last 24 hours. Hover over the cell to see a summary of recent alerts. Click links in the pop-up to view details for each alert. For more information, refer to [Alerts](https://docs.newrelic.com/docs/alerts/overview/) and [Issues](https://docs.newrelic.com/docs/alerts/incident-management/Issues-and-Incident-management-and-response/).</td>
+        </tr>
+        <tr>
+            <td>Region</td>
+            <td>The geographic location or cloud provider region where the resource is deployed. This helps you understand data locality, latency, and compliance. The Region value is populated automatically by checking for values across a prioritized list of metadata tags. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
+            The following tags are checked in order: 
+            <ul>
+                <li>`region`</li>
+                <li>`cloud.region`</li>
+                <li>`aws.region`</li>
+                <li>`awsRegion`</li>
+                <li>`azure.regionName`</li>
+                <li>`gcp.region`</li>
+            </ul>
+            </td>
+        </tr>
+        <tr>
+            <td>Availability Zone</td>
+            <td>The isolated location within a cloud region where the resource is deployed. This is used for fault tolerance and high availability by distributing resources across multiple zones. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
+            The following tags are checked in order: 
+            <ul>
+                <li>`availabilityZone`</li>
+                <li>`cloud.availability_Zone`</li>
+                <li>`aws.availabilityZone`</li>
+                <li>`awsAvailabilityZone`</li>
+                <li>`azure.availabilityZone`</li>
+                <li>`gcp.zone`</li>
+            </ul>
+            </td>
+        </tr>
+        <tr>
+            <td>Environment</td>
+            <td>The stage or purpose of the resource in the software lifecycle. For example, `development`, `staging`, or `production`. This helps teams manage stability, testing, and deployment workflows. The first non-empty value found is used, which ensures consistent classification even when naming conventions vary. 
+            The following tags are checked in order: 
+            <ul>
+                <li>`Environment`</li>
+                <li>`environment`</li>
+                <li>`env`</li>
+            </ul>
+            </td>
+        </tr>
+    </tbody>
+</table>
+
+## Add new data [#add-new-data]
+
+To add additional data to your Infrastructure catalog click the + Add Data button at the top right. Follow the on screen instructions to add data to your Infrastructure catalog. For more information on New Relic supported integrations, refer [Integrations](https://newrelic.com/instant-observability/).
+
+
+### Limitations [#limitations]
+
+* No support for sorting data in the Infrastructure catalog page.
\ No newline at end of file
diff --git a/src/content/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/content/docs/service-architecture-intelligence/catalogs/repository-catalog.mdx
similarity index 95%
rename from src/content/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
rename to src/content/docs/service-architecture-intelligence/catalogs/repository-catalog.mdx
index b3406327274..7519647a351 100644
--- a/src/content/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ b/src/content/docs/service-architecture-intelligence/catalogs/repository-catalog.mdx
@@ -9,18 +9,19 @@ freshnessValidatedDate: never
 ---
 
 
-<Callout title="Preview">
-    We're still working on this feature, but we'd love for you to try it out!
-
-    This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
-
 
 The <DNT>Repository catalog</DNT> is a tool designed to centralize and streamline the management of repositories within an organization. By providing a unified view of all repositories, it enhances cross-team collaboration and simplifies the discovery, access, and management of code repositories. 
 
 The <DNT>Repository catalog</DNT> is designed to break silos between teams and increase cross-team collaboration. It enables developers, Site Reliability Engineers (SREs), and other stakeholders to efficiently identify existing repositories, understand their purpose, and determine ownership or status. This centralized approach leads to improved collaboration, accountability, and productivity across the organization.
 
 
+<Callout variant="important">
+
+    The Repository catalogs feature is available only to Advanced Compute customers. To learn more about our pricing model, editions, and buying programs, refer to the [pricing documentation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/).
+    
+</Callout>
+
+
 ## Key features [#features]
 
 -  **Centralized Repository Discovery:** Quickly identify repositories relevant to services, projects, or <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, minimizing the time spent searching or consulting with colleagues.
diff --git a/src/i18n/content/es/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/i18n/content/es/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
deleted file mode 100644
index 139447a7246..00000000000
--- a/src/i18n/content/es/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: catálogo de repositorio
-tag:
-  - Service Architecture Intelligence
-  - Repository
-  - Catalog
-metaDescription: The Repository catalog is a tool designed to centralize and streamline the management of repositories within an organization.
-freshnessValidatedDate: never
-translationType: machine
----
-
-<Callout title="Avance">
-  Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras!
-
-  Esta función se proporciona actualmente como parte de una vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
-
-<DNT>Repository catalog</DNT> es una herramienta diseñada para centralizar y agilizar la gestión del repositorio dentro de una organización. Al proporcionar una vista unificada de todo el repositorio, mejora la colaboración entre equipos y simplifica el descubrimiento, el acceso y la gestión del repositorio de código.
-
-El <DNT>Repository catalog</DNT> está diseñado para romper el aislamiento entre equipos y aumentar la colaboración entre equipos. Permite a los desarrolladores, ingenieros de confiabilidad del sitio (SRE) y otras partes interesadas identificar eficientemente el repositorio existente, comprender su propósito y determinar la propiedad o el estado. Este enfoque centralizado conduce a una mejor colaboración, responsabilidad y productividad en toda la organización.
-
-## Característica clave [#features]
-
-* **Descubrimiento de repositorios centralizado:** identifique rápidamente repositorios relevantes para servicios, proyectos o <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, minimizando el tiempo dedicado a buscar o consultar con colegas.
-
-* **Navegación entre servicios y repositorios:** navegue sin problemas desde aplicaciones o servicios hasta su repositorio de definición y viceversa, lo que ayuda a comprender la dependencia del código y la infraestructura.
-
-* **Propiedad y responsabilidad:** identifique fácilmente a los propietarios de los repositorios, lo que respalda la consulta directa y mejora la responsabilidad dentro de los equipos.
-
-* **Insights del repositorio:** acceda a métricas detalladas sobre la actividad del repositorio, como solicitudes de extracción abiertas e historial de implementación, para identificar proyectos desatendidos y optimizar la asignación de recursos.
-
-* **Gestión y Operaciones:** Realizar operaciones masivas, como asignar etiquetas o equipos, para gestionar eficientemente el repositorio y mantener los estándares organizacionales.
-
-## Acceder al catálogo del repositorio [#access-repository]
-
-**Prerrequisitos:**
-
-* Habilite los catálogos en su cuenta de New Relic. Para obtener más información, consulte [Habilitar los catálogos](/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs).
-
-**Para acceder al inventario del catálogo del repositorio:**
-
-1. Inicie sesión en su plataforma New Relic.
-
-2. Vaya al **panel de navegación izquierdo &gt; Catalogs &gt; Repository catalog**.
-
-   <img title="Repository catalogs" alt="RepositoryCatalog" src="/images/new-relic-repository-catalog.webp" />
-
-El <DNT>Repository catalog</DNT> muestra todos los repositorios vinculados y la información relacionada:
-
-<table>
-  <thead>
-    <tr>
-      <th>
-        UI
-      </th>
-
-      <th>
-        Descripción
-      </th>
-    </tr>
-  </thead>
-
-  <tbody>
-    <tr>
-      <td>
-        <DNT>Name</DNT>
-      </td>
-
-      <td>
-        El nombre del repositorio. Haga clic para abrir el panel de detalles del repositorio en el lado derecho. Este panel de detalles contiene información como descripción general del repositorio, entidad vinculada con el repositorio, etiqueta y más.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Description</DNT>
-      </td>
-
-      <td>
-        La descripción del repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Origin/Source</DNT>
-      </td>
-
-      <td>
-        Muestra la información donde está alojado este repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Organization</DNT>
-      </td>
-
-      <td>
-        Organización GitHub desde donde se importó el repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Team</DNT>
-      </td>
-
-      <td>
-        El equipo responsable de la entidad. Haga clic en el nombre del equipo para ir a la página central del equipo correspondiente para ver más información sobre la gestión de la entidad por parte del equipo. Pase el mouse sobre el enlace 
-
-        <DNT>Team</DNT>
-
-         para ver detalles adicionales en el cuadro de diálogo emergente. Si un equipo no está asignado a una entidad, haga clic en el botón 
-
-        <DNT>Assign Team</DNT>
-
-         y seleccione el equipo responsable de la lista mostrada. Para obtener más información, consulte 
-
-        [Equipos](/docs/service-architecture-intelligence/teams/teams)
-
-        .
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        La fecha y hora del último despliegue. Haga clic en el enlace para ver los detalles del cambio y su impacto. Para obtener más información, consulte 
-
-        [seguimiento de cambios.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Entities</DNT>
-      </td>
-
-      <td>
-        El número de entidad vinculada con el repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>URL</DNT>
-      </td>
-
-      <td>
-        La URL para acceder al repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        La fecha y hora del último despliegue. Haga clic en el enlace para ver los detalles del cambio y su impacto. Para obtener más información, consulte 
-
-        [seguimiento de cambios.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Open PRs</DNT>
-      </td>
-
-      <td>
-        Muestra el número de solicitudes de extracción abiertas en el repositorio.Pase el mouse sobre el enlace para ver detalles adicionales en el cuadro de diálogo emergente.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Creation Date</DNT>
-      </td>
-
-      <td>
-        Muestra la fecha en la que se creó el repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Update</DNT>
-      </td>
-
-      <td>
-        Muestra la fecha en que se actualiza el repositorio.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Primary Language</DNT>
-      </td>
-
-      <td>
-        Muestra el idioma más empleado en el repositorio.
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-### Agregar nuevos datos [#add-new-data]
-
-Para agregar datos adicionales a tu <DNT>Repository catalog</DNT> haz clic en el botón **+ Add GitHub repositories** en la parte superior derecha. Siga las instrucciones en pantalla para agregar datos a su repositorio. Para obtener información adicional para agregar repositorio, consulte [Integración de GitHub.](/docs/service-architecture-intelligence/github-integration)
-
-### Limitaciones [#limitations]
-
-* No hay soporte para ordenar datos en la página <DNT>Repository catalog</DNT> .
-* En ciertos escenarios, es posible que las vistas almacenadas no funcionen como se espera en <DNT>Repository catalog</DNT>.
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/i18n/content/fr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
deleted file mode 100644
index 667cd4000e8..00000000000
--- a/src/i18n/content/fr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: catalogue référentiel
-tag:
-  - Service Architecture Intelligence
-  - Repository
-  - Catalog
-metaDescription: The Repository catalog is a tool designed to centralize and streamline the management of repositories within an organization.
-freshnessValidatedDate: never
-translationType: machine
----
-
-<Callout title="Aperçu">
-  Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l&apos;essayiez !
-
-  Cette fonctionnalité est actuellement fournie dans le cadre d&apos;un aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
-
-Le <DNT>Repository catalog</DNT> est un outil conçu pour centraliser et rationaliser la gestion du référentiel au sein d&apos;une organisation. En fournissant une vue unifiée de tous les référentiels, il améliore la collaboration entre les équipes et simplifie la découverte, l&apos;accès et la gestion du référentiel de code.
-
-Le <DNT>Repository catalog</DNT> est conçu pour briser les silos entre les équipes et augmenter la collaboration entre les équipes. Il permet aux développeurs, aux ingénieurs fiabilité des sites (SRE) et à d&apos;autres parties prenantes d&apos;identifier efficacement les référentiels existants, de comprendre leur objectif et de déterminer leur propriété ou leur statut. Cette approche centralisée conduit à une amélioration de la collaboration, de la responsabilité et de la productivité dans l’ensemble de l’organisation.
-
-## Fonctionnalité clé [#features]
-
-* **Découverte centralisée de référentiels :** Identifiez rapidement les référentiels pertinents pour les services, les projets ou <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, en minimisant le temps passé à rechercher ou à consulter un collègue.
-
-* **Service et référentiel Navigation :** Naviguez de manière transparente depuis les applications ou les services vers leur référentiel de définition et vice versa, aidant à comprendre la dépendance du code et infrastructure.
-
-* **Propriété et responsabilité :** identifiez facilement les propriétaires de référentiel, prenez en charge les requêtes directes et améliorez la responsabilité au sein des équipes.
-
-* **référentiel Insights:** accédez à des mesures détaillées sur l&apos;activité du référentiel, telles que la demande de tirage ouverte et l&apos;historique de déploiement, pour identifier les projets négligés et optimiser l&apos;allocation des ressources.
-
-* **Gestion et opérations :** Effectuer des opérations en masse, telles que l&apos;attribution d&apos;étiquettes ou d&apos;équipes, pour gérer efficacement le référentiel et maintenir les normes organisationnelles.
-
-## Accéder au catalogue référentiel [#access-repository]
-
-**Prérequis :**
-
-* Activez les catalogues dans votre compte New Relic. Pour plus d&apos;informations, reportez-vous [à Activer les catalogues](/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs).
-
-**Pour accéder à l&apos;inventaire du catalogue du référentiel :**
-
-1. connectez-vous à votre plateforme New Relic.
-
-2. Accédez au **volet de navigation de gauche &gt; Catalogs &gt; Repository catalog**.
-
-   <img title="Repository catalogs" alt="RepositoryCatalog" src="/images/new-relic-repository-catalog.webp" />
-
-Le <DNT>Repository catalog</DNT> affiche tous les référentiels liés et les informations associées :
-
-<table>
-  <thead>
-    <tr>
-      <th>
-        UI
-      </th>
-
-      <th>
-        Description
-      </th>
-    </tr>
-  </thead>
-
-  <tbody>
-    <tr>
-      <td>
-        <DNT>Name</DNT>
-      </td>
-
-      <td>
-        Le nom du référentiel. Cliquez pour ouvrir le volet des détails du référentiel sur le côté droit. Ce volet de détails contient des informations telles que l&apos;aperçu du référentiel, le référentiel d&apos;entité lié à, la balise, etc.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Description</DNT>
-      </td>
-
-      <td>
-        La description du référentiel.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Origin/Source</DNT>
-      </td>
-
-      <td>
-        Affiche les informations où ce référentiel est hébergé.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Organization</DNT>
-      </td>
-
-      <td>
-        Organisation GitHub d&apos;où les référentiels ont été importés.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Team</DNT>
-      </td>
-
-      <td>
-        L&apos;équipe responsable de l&apos;entité. Cliquez sur le nom de l&apos;équipe pour accéder à la page centrale de l&apos;équipe correspondante afin d&apos;afficher plus d&apos;informations sur l&apos;équipe qui gère l&apos;entité. Passez la souris sur le lien 
-
-        <DNT>Team</DNT>
-
-         pour afficher des détails supplémentaires dans la boîte de dialogue contextuelle. Si une équipe n’est pas affectée à une entité, cliquez sur le bouton 
-
-        <DNT>Assign Team</DNT>
-
-         et sélectionnez l’équipe responsable dans la liste affichée. Pour plus d&apos;informations, reportez-vous 
-
-        [à Teams](/docs/service-architecture-intelligence/teams/teams)
-
-        .
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        La date et l&apos;heure du dernier déploiement. Cliquez sur le lien pour voir les détails du changement et son impact. Pour plus d’informations, consultez 
-
-        [suivi des changements.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Entities</DNT>
-      </td>
-
-      <td>
-        Le nombre d&apos;entités liées au référentiel.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>URL</DNT>
-      </td>
-
-      <td>
-        L&apos;URL pour accéder au référentiel.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        La date et l&apos;heure du dernier déploiement. Cliquez sur le lien pour voir les détails du changement et son impact. Pour plus d’informations, consultez 
-
-        [suivi des changements.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Open PRs</DNT>
-      </td>
-
-      <td>
-        Affiche le nombre de demandes de tirage ouvertes dans le référentiel. Passez la souris sur le lien pour afficher des détails supplémentaires dans la boîte de dialogue contextuelle.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Creation Date</DNT>
-      </td>
-
-      <td>
-        Affiche la date de création du référentiel.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Update</DNT>
-      </td>
-
-      <td>
-        Affiche la date à laquelle le référentiel est mis à jour.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Primary Language</DNT>
-      </td>
-
-      <td>
-        Affiche la langue la plus utilisée dans le référentiel.
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-### Ajouter de nouvelles données [#add-new-data]
-
-Pour ajouter des données supplémentaires à votre <DNT>Repository catalog</DNT> , cliquez sur le bouton **+ Add GitHub repositories** en haut à droite. Suivez les instructions à l&apos;écran pour ajouter des données à votre référentiel. Pour plus d’informations sur l’ajout d’un référentiel, reportez-vous à [l’intégration GitHub.](/docs/service-architecture-intelligence/github-integration)
-
-### Limites [#limitations]
-
-* Aucune prise en charge du tri des données dans la page <DNT>Repository catalog</DNT> .
-* Dans certains scénarios, les vues enregistrées peuvent ne pas fonctionner comme prévu dans le <DNT>Repository catalog</DNT>.
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/i18n/content/jp/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
deleted file mode 100644
index ae2d8b5d5a9..00000000000
--- a/src/i18n/content/jp/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: リポジトリカタログ
-tag:
-  - Service Architecture Intelligence
-  - Repository
-  - Catalog
-metaDescription: The Repository catalog is a tool designed to centralize and streamline the management of repositories within an organization.
-freshnessValidatedDate: never
-translationType: machine
----
-
-<Callout title="プレビュー">
-  この機能はまだ開発中ですが、ぜひお試しください。
-
-  この機能は現在、弊社の[プレリリース ポリシー](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/)に従ってプレビューの一部として提供されています。
-</Callout>
-
-<DNT>Repository catalog</DNT> 、組織内のリポジトリの管理を一元化および合理化するために設計されたツールです。 すべてのリポジトリの統一されたビューを提供することで、チーム間のコラボレーションが強化され、コード リポジトリの検出、アクセス、管理が簡素化されます。
-
-<DNT>Repository catalog</DNT> 、チーム間のサイロを解消し、チーム間のコラボレーションを強化するように設計されています。 これにより、開発者、サイト信頼性エンジニア (SRE)、およびその他の関係者は、既存のリポジトリを効率的に識別し、その目的を理解し、所有権やステータスを決定できるようになります。 この集中化されたアプローチにより、組織全体のコラボレーション、説明責任、生産性が向上します。
-
-## 主な特徴 [#features]
-
-* **一元的なリポジトリ検出:**サービス、プロジェクト、または<DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>に関連するリポジトリを迅速に特定し、検索や同僚との相談に費やす時間を最小限に抑えます。
-
-* **サービスとリポジトリのナビゲーション:**アプリケーションまたはサービスからその定義リポジトリへ、またはその逆にシームレスに移動し、コードの依存関係とインフラストラクチャの理解を支援します。
-
-* **所有権と説明責任:**リポジトリの所有者を簡単に識別し、直接クエリをサポートし、チーム内の説明責任を強化します。
-
-* **リポジトリInsights :**オープンプルリクエストやデプロイメント履歴など、リポジトリアクティビティに関する詳細なメトリクスにアクセスして、放置されているプロジェクトを特定し、リソース割り当てを最適化します。
-
-* **管理と運用:**タグやチームの割り当てなどの一括操作を実行して、リポジトリを効率的に管理し、組織の標準を維持します。
-
-## リポジトリカタログにアクセスする [#access-repository]
-
-**前提条件:**
-
-* New Relic アカウントでカタログを有効にします。 詳細については、 [「カタログを有効にする」](/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs)を参照してください。
-
-**リポジトリ カタログ インベントリにアクセスするには:**
-
-1. New Relic プラットフォームにログインします。
-
-2. **左側のナビゲーション ペイン &gt; Catalogs &gt; Repository catalog**に移動します。
-
-   <img title="Repository catalogs" alt="RepositoryCatalog" src="/images/new-relic-repository-catalog.webp" />
-
-<DNT>Repository catalog</DNT>には、リンクされたすべてのリポジトリと関連情報が表示されます。
-
-<table>
-  <thead>
-    <tr>
-      <th>
-        UI
-      </th>
-
-      <th>
-        説明
-      </th>
-    </tr>
-  </thead>
-
-  <tbody>
-    <tr>
-      <td>
-        <DNT>Name</DNT>
-      </td>
-
-      <td>
-        リポジトリの名前。 クリックすると、右側のリポジトリの詳細ペインが開きます。 この詳細ペインには、リポジトリの概要、リポジトリにリンクされているエンティティ、タグなどの情報が含まれています。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Description</DNT>
-      </td>
-
-      <td>
-        リポジトリの説明。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Origin/Source</DNT>
-      </td>
-
-      <td>
-        このリポジトリがホストされている場所の情報を表示します。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Organization</DNT>
-      </td>
-
-      <td>
-        リポジトリがインポートされた GitHub 組織。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Team</DNT>
-      </td>
-
-      <td>
-        エンティティを担当するチーム。 チーム名をクリックすると、対応するチームのハブ ページに移動し、エンティティを管理しているチームの詳細情報が表示されます。 
-
-        <DNT>Team</DNT>
-
-        リンクにマウスを移動すると、ポップアップ ダイアログ ボックスに追加の詳細が表示されます。 チームがエンティティに割り当てられていない場合は、 
-
-        <DNT>Assign Team</DNT>
-
-        ボタンをクリックし、表示されたリストから担当チームを選択します。 詳細については、 
-
-        [Teams](/docs/service-architecture-intelligence/teams/teams)
-
-        を参照してください。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        最後のデプロイメントの日時。 リンクをクリックすると、変更の詳細とその影響が表示されます。 詳細については、 
-
-        [「変更追跡 (変更追跡機能)」を参照してください。](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Entities</DNT>
-      </td>
-
-      <td>
-        リポジトリにリンクされているエンティティの数。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>URL</DNT>
-      </td>
-
-      <td>
-        リポジトリにアクセスするための URL。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        最後のデプロイメントの日時。 リンクをクリックすると、変更の詳細とその影響が表示されます。 詳細については、 
-
-        [「変更追跡 (変更追跡機能)」を参照してください。](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Open PRs</DNT>
-      </td>
-
-      <td>
-        リポジトリ内のオープンプルリクエストの数を表示します。 リンクにマウスを移動すると、ポップアップ ダイアログ ボックスに追加の詳細が表示されます。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Creation Date</DNT>
-      </td>
-
-      <td>
-        リポジトリが作成された日付を表示します。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Update</DNT>
-      </td>
-
-      <td>
-        リポジトリが更新された日付を表示します。
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Primary Language</DNT>
-      </td>
-
-      <td>
-        リポジトリ内で最も使用されている言語を表示します。
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-### 新しいデータを追加する [#add-new-data]
-
-<DNT>Repository catalog</DNT>に追加データを追加するには、右上にある**+ Add GitHub repositories** \[+ GitHub リポジトリの追加]ボタンをクリックします。 画面上の指示に従って、リポジトリにデータを追加します。 リポジトリを追加するための追加情報については、 [GitHub インテグレーションを参照してください。](/docs/service-architecture-intelligence/github-integration)
-
-### 制限 [#limitations]
-
-* <DNT>Repository catalog</DNT>ページではデータの並べ替えはサポートされていません。
-* 特定のシナリオでは、保存されたビューが<DNT>Repository catalog</DNT>で意図したとおりに機能しない場合があります。
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/i18n/content/kr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
deleted file mode 100644
index 041b640b3fc..00000000000
--- a/src/i18n/content/kr/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: 저장소 카탈로그
-tag:
-  - Service Architecture Intelligence
-  - Repository
-  - Catalog
-metaDescription: The Repository catalog is a tool designed to centralize and streamline the management of repositories within an organization.
-freshnessValidatedDate: never
-translationType: machine
----
-
-<Callout title="시사">
-  이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다!
-
-  이 기능은 현재 [사전 출시 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/) 에 따라 미리보기의 일부로 제공됩니다.
-</Callout>
-
-<DNT>Repository catalog</DNT> 은 조직 내 저장소 관리를 중앙화하고 간소화하도록 설계된 도구입니다. 모든 저장소에 대한 통합된 보기를 제공함으로써 팀 간 협업을 강화하고 코드 저장소의 검색, 액세스 및 관리를 간소화합니다.
-
-<DNT>Repository catalog</DNT> 은 팀 간의 고립을 해소하고 팀 간 협업을 늘리도록 설계되었습니다. 이를 통해 개발자, 사이트 안정성 엔지니어(SRE) 및 기타 이해 관계자는 기존 저장소를 효율적으로 식별하고, 그 목적을 이해하고, 소유권 또는 상태를 결정할 수 있습니다. 이러한 중앙 집중화된 접근 방식은 조직 전체에서 협업, 책임성, 생산성을 향상시킵니다.
-
-## 주요 특징들 [#features]
-
-* **중앙 집중식 저장소 검색:** 서비스, 프로젝트 또는 <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT> 와 관련된 저장소를 신속하게 식별하여 검색하거나 동료와 상의하는 데 소요되는 시간을 최소화합니다.
-
-* **서비스 및 개체 탐색:** 포함 또는 서비스에서 대상 정의로 또는 그 반대로 원활하게 탐색하여 코드 의존성/종속성 및 감시를 이해하는 데 도움을 줍니다.
-
-* **소유권 및 책임:** 저장소 소유자를 쉽게 식별하여 직접 쿼리를 지원하고 팀 내 책임을 강화합니다.
-
-* **로그 Insights:** 공개 풀 요청 및 구현, 배포 이력 등의 적용 활동에 대한 세부 지표에 액세스하여 소홀히 된 프로젝트를 식별하고 리소스 할당을 최적화합니다.
-
-* **관리 및 운영:** 태그나 팀을 할당하는 등의 대량 작업을 수행하여 저장소를 효율적으로 관리하고 조직 표준을 유지합니다.
-
-## 저장소 카탈로그에 액세스하세요 [#access-repository]
-
-**필수 조건:**
-
-* 뉴렐릭 계정에서 카탈로그를 활성화하세요. 자세한 내용은 [카탈로그 활성화를](/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs) 참조하세요.
-
-**저장소 카탈로그 인벤토리에 액세스하려면:**
-
-1. 뉴렐릭 플랫폼에 로그인하세요.
-
-2. **왼쪽 탐색 창 &gt; Catalogs &gt; Repository catalog** 로 이동합니다.
-
-   <img title="Repository catalogs" alt="RepositoryCatalog" src="/images/new-relic-repository-catalog.webp" />
-
-<DNT>Repository catalog</DNT> 은 모든 링크된 저장소와 관련 정보를 표시합니다.
-
-<table>
-  <thead>
-    <tr>
-      <th>
-        UI
-      </th>
-
-      <th>
-        설명
-      </th>
-    </tr>
-  </thead>
-
-  <tbody>
-    <tr>
-      <td>
-        <DNT>Name</DNT>
-      </td>
-
-      <td>
-        저장소의 이름. 오른쪽에 있는 저장소 세부정보 창을 열려면 클릭하세요. 이 세부정보 창에는 구성원 개요, 구성원과 연결된 구성원, 태그 등의 정보가 포함되어 있습니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Description</DNT>
-      </td>
-
-      <td>
-        저장소에 대한 설명.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Origin/Source</DNT>
-      </td>
-
-      <td>
-        이 저장소가 호스팅되는 위치를 표시합니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Organization</DNT>
-      </td>
-
-      <td>
-        GitHub는 리포지터리를 가져온 곳에서 조직합니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Team</DNT>
-      </td>
-
-      <td>
-        정보의 책임 팀입니다. 팀 이름을 클릭하면 해당 팀의 허브 페이지로 이동하여 해당 기관을 관리하는 팀에 대한 자세한 정보를 볼 수 있습니다. 팝업 대화 상자에서 추가 세부 정보를 보려면 마우스를 
-
-        <DNT>Team</DNT>
-
-         링크에 올려 놓으세요. 팀이 개념에 할당되지 않은 경우, 
-
-        <DNT>Assign Team</DNT>
-
-         버튼을 클릭하고 표시된 목록에서 책임 팀을 선택하세요. 자세한 내용은 
-
-        [팀을](/docs/service-architecture-intelligence/teams/teams)
-
-         참조하세요.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        마지막 구현의 날짜와 시간, 배포. 링크를 클릭하면 변경 사항과 그 영향에 대한 자세한 내용을 볼 수 있습니다. 자세한 내용은 
-
-        [추적 변경을 참조하세요.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Entities</DNT>
-      </td>
-
-      <td>
-        부품과 연결된 부품의 수입니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>URL</DNT>
-      </td>
-
-      <td>
-        저장소에 접근하는 URL입니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        마지막 구현의 날짜와 시간, 배포. 링크를 클릭하면 변경 사항과 그 영향에 대한 자세한 내용을 볼 수 있습니다. 자세한 내용은 
-
-        [추적 변경을 참조하세요.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Open PRs</DNT>
-      </td>
-
-      <td>
-        현재 위치에 Open Pull 요청 횟수를 표시합니다. 추가 세부 정보를 보려면 마우스를 링크 위에 올려 놓으세요. 팝업 대화 상자가 나타납니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Creation Date</DNT>
-      </td>
-
-      <td>
-        저장소가 생성된 날짜를 표시합니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Update</DNT>
-      </td>
-
-      <td>
-        저장소가 업데이트된 날짜를 표시합니다.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Primary Language</DNT>
-      </td>
-
-      <td>
-        저장소에서 가장 많이 사용되는 언어를 표시합니다.
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-### 새로운 데이터 추가 [#add-new-data]
-
-<DNT>Repository catalog</DNT> 에 추가 데이터를 추가하려면 오른쪽 상단에 있는 **+ Add GitHub repositories** \[+ GitHub 저장소 추가] 버튼을 클릭하세요. 화면의 지시에 따라 저장소에 데이터를 추가하세요. 저장소를 추가하는 방법에 대한 자세한 내용은 [GitHub 통합을 참조하세요.](/docs/service-architecture-intelligence/github-integration)
-
-### 제한 사항 [#limitations]
-
-* <DNT>Repository catalog</DNT> 페이지에서 데이터 정렬을 지원하지 않습니다.
-* 특정 시나리오에서는 저장된 보기가 <DNT>Repository catalog</DNT> 에서 의도한 대로 작동하지 않을 수 있습니다.
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx b/src/i18n/content/pt/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
deleted file mode 100644
index 8e304ff7edc..00000000000
--- a/src/i18n/content/pt/docs/service-architecture-intelligence/catalogs/repositoryCatalog.mdx
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: Catálogo de repositório
-tag:
-  - Service Architecture Intelligence
-  - Repository
-  - Catalog
-metaDescription: The Repository catalog is a tool designed to centralize and streamline the management of repositories within an organization.
-freshnessValidatedDate: never
-translationType: machine
----
-
-<Callout title="Visualização">
-  Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse!
-
-  Atualmente, esse recurso é fornecido como parte de uma prévia, de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
-</Callout>
-
-O <DNT>Repository catalog</DNT> é uma ferramenta desenvolvida para centralizar e agilizar a gestão do repositório dentro de uma organização. Ao fornecer uma visão unificada de todo o repositório, ele aprimora a colaboração entre equipes e simplifica a descoberta, o acesso e o gerenciamento do repositório de código.
-
-O <DNT>Repository catalog</DNT> foi projetado para quebrar silos entre equipes e aumentar a colaboração entre equipes. Ele permite que desenvolvedores, engenheiros de confiabilidade do site (SREs) e outras partes interessadas identifiquem com eficiência o repositório existente, entendam sua finalidade e determinem a propriedade ou status. Essa abordagem centralizada leva a uma melhor colaboração, responsabilização e produtividade em toda a organização.
-
-## Recurso chave [#features]
-
-* **Descoberta de repositório centralizado:** identifique rapidamente o repositório relevante para serviços, projetos ou <DNT>[Teams](/docs/service-architecture-intelligence/teams/teams)</DNT>, minimizando o tempo gasto pesquisando ou consultando o colega.
-
-* **Navegação de serviços e repositórios:** navegue facilmente do aplicativo ou serviços até seu repositório definidor e vice-versa, auxiliando na compreensão da dependência e infraestrutura do código.
-
-* **Propriedade e responsabilidade:** identifique facilmente os proprietários do repositório, apoiando a consultoria direta e aumentando a responsabilidade dentro das equipes.
-
-* **Insights do repositório:** Acesse métricas detalhadas sobre a atividade do repositório, como open pull request e histórico de implantação, para identificar projetos negligenciados e otimizar a alocação de recursos.
-
-* **Gerenciamento e operações:** execute operações em massa, como atribuição de tags ou equipes, para gerenciar o repositório com eficiência e manter os padrões organizacionais.
-
-## Acesse o catálogo do repositório [#access-repository]
-
-**Pré-requisitos:**
-
-* Habilite os Catálogos na sua conta New Relic. Para obter mais informações, consulte [Habilitar os catálogos](/docs/service-architecture-intelligence/catalogs/catalogs/#enable-catalogs).
-
-**Para acessar o inventário do catálogo do repositório:**
-
-1. Entre na sua plataforma New Relic.
-
-2. Vá para o **painel de navegação esquerdo &gt; Catalogs &gt; Repository catalog**.
-
-   <img title="Repository catalogs" alt="RepositoryCatalog" src="/images/new-relic-repository-catalog.webp" />
-
-O <DNT>Repository catalog</DNT> exibe todos os repositórios vinculados e informações relacionadas:
-
-<table>
-  <thead>
-    <tr>
-      <th>
-        UI
-      </th>
-
-      <th>
-        Descrição
-      </th>
-    </tr>
-  </thead>
-
-  <tbody>
-    <tr>
-      <td>
-        <DNT>Name</DNT>
-      </td>
-
-      <td>
-        O nome do repositório. Clique para abrir o painel de detalhes do repositório no lado direito. Este painel de detalhes contém informações como visão geral do repositório, entidade do repositório vinculada, tag e muito mais.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Description</DNT>
-      </td>
-
-      <td>
-        A descrição do repositório.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Origin/Source</DNT>
-      </td>
-
-      <td>
-        Exibe as informações de onde este repositório está hospedado.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Organization</DNT>
-      </td>
-
-      <td>
-        Organização GitHub de onde o repositório foi importado.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Team</DNT>
-      </td>
-
-      <td>
-        A equipe responsável pela entidade. Clique no nome da equipe para ir para a página central da equipe correspondente e ver mais informações sobre a equipe que gerencia a entidade. Passe o mouse sobre o link 
-
-        <DNT>Team</DNT>
-
-         para ver detalhes adicionais na caixa de diálogo pop-up. Se uma equipe não estiver atribuída a uma entidade, clique no botão 
-
-        <DNT>Assign Team</DNT>
-
-         e selecione a equipe responsável na lista exibida. Para mais informações, consulte 
-
-        [Equipes](/docs/service-architecture-intelligence/teams/teams)
-
-        .
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        A data e hora da última implantação. Clique no link para ver detalhes da mudança e seu impacto. Para mais informações consulte 
-
-        [Monitoramento de Alterações.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Entities</DNT>
-      </td>
-
-      <td>
-        O número da entidade vinculada ao repositório.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>URL</DNT>
-      </td>
-
-      <td>
-        A URL para acessar o repositório.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Deploy</DNT>
-      </td>
-
-      <td>
-        A data e hora da última implantação. Clique no link para ver detalhes da mudança e seu impacto. Para mais informações consulte 
-
-        [Monitoramento de Alterações.](/docs/change-tracking/change-tracking-introduction/)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Open PRs</DNT>
-      </td>
-
-      <td>
-        Exibe o número de pull requests abertas no repositório. Passe o mouse sobre o link para ver detalhes adicionais na caixa de diálogo pop-up.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Creation Date</DNT>
-      </td>
-
-      <td>
-        Exibe a data em que o repositório foi criado.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Last Update</DNT>
-      </td>
-
-      <td>
-        Exibe a data em que o repositório é atualizado.
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        <DNT>Primary Language</DNT>
-      </td>
-
-      <td>
-        Exibe o idioma mais usado no repositório.
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-### Adicionar novos dados [#add-new-data]
-
-Para adicionar dados adicionais ao seu <DNT>Repository catalog</DNT> , clique no botão **+ Add GitHub repositories** no canto superior direito. Siga as instruções na tela para adicionar dados ao seu repositório. Para obter informações adicionais sobre como adicionar repositório, consulte [GitHub integração.](/docs/service-architecture-intelligence/github-integration)
-
-### Limitações [#limitations]
-
-* Não há suporte para classificação de dados na página <DNT>Repository catalog</DNT> .
-* Em certos cenários, as visualizações salvas podem não funcionar conforme o esperado no <DNT>Repository catalog</DNT>.
\ No newline at end of file
diff --git a/src/nav/service-architecture-intelligence.yml b/src/nav/service-architecture-intelligence.yml
index 56b1e8d82fb..ea1a19d8dcf 100644
--- a/src/nav/service-architecture-intelligence.yml
+++ b/src/nav/service-architecture-intelligence.yml
@@ -16,7 +16,9 @@ pages:
         - title: Applications catalog
           path: /docs/service-architecture-intelligence/catalogs/applications-catalog
         - title: Repository catalog
-          path: /docs/service-architecture-intelligence/catalogs/repositoryCatalog
+          path: /docs/service-architecture-intelligence/catalogs/repository-catalog
+        - title: Infrastructure catalog
+          path: /docs/service-architecture-intelligence/catalogs/infrastructure-catalog
       - title: Scorecards
         pages:
         - title: Getting started with Scorecards
diff --git a/static/images/infracatalogs.webp b/static/images/infracatalogs.webp
new file mode 100644
index 00000000000..557ee0bad6e
Binary files /dev/null and b/static/images/infracatalogs.webp differ