diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 24fd0bc2..3cf5c564 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,4 +1,4 @@ Contributions ============= -TODO +See [Provide Feedback on a Page](https://github.com/canton-network/cf-docs#provide-feedback-on-a-page). diff --git a/README.md b/README.md index 27265bbc..cb6d3eda 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -Copyright (c) 2025 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved. +Copyright (c) 2026 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved. SPDX-License-Identifier: Apache-2.0 AND CC-BY-4.0 docs diff --git a/docs-main/global-synchronizer/deployment/prerequisites.mdx b/docs-main/global-synchronizer/deployment/prerequisites.mdx index 0e6db0c0..c07b42c1 100644 --- a/docs-main/global-synchronizer/deployment/prerequisites.mdx +++ b/docs-main/global-synchronizer/deployment/prerequisites.mdx @@ -3,14 +3,6 @@ title: "Prerequisites" description: "System requirements for running a validator on the Canton Network" --- -{/* COPIED_START source="splice:docs/src/validator_operator/validator_hardware_requirements.rst" hash="22640d55" */} - - -This section was copied from existing reviewed documentation. -**Source:** `docs/src/validator_operator/validator_hardware_requirements.rst` -Reviewers: Skip this section. Remove markers after final approval. - - This section describes hardware requirements for running a validator. Note that these are reference values. Actual requirements can vary based on usage of your validator. We recommend monitoring your production validator nodes with respect to CPU and memory usage of all components and disk usage of the database, and adjust the resourcing as needed. The requirements include both the validator and participant container. @@ -26,6 +18,3 @@ These requirements are largely identical between the docker-compose based deploy ## Database Latency Components are relatively sensitive to database latency. If you use a managed database offering like GCP CloudSQL, it is recommended that you allocate it in the same region and zone that your cluster runs in. - - -{/* COPIED_END */} \ No newline at end of file