Merge pull request #3045 from Blargian/3039_fix_broken_hash_docs_repo

update broken hashes for cloud

Author: gingerwizard

docs/en/cloud/bestpractices/partitioningkey.md

@@ -4,7 +4,7 @@ sidebar_label: Choose a Low Cardinality Partitioning Key
 title: Choose a Low Cardinality Partitioning Key
 ---
 
-When you send an insert statement (that should contain many rows - see [section above](#ingest-data-in-bulk)) to a table in ClickHouse Cloud, and that
+When you send an insert statement (that should contain many rows - see [section above](/docs/en/optimize/bulk-inserts)) to a table in ClickHouse Cloud, and that
 table is not using a [partitioning key](/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key.md) then all row data from that insert is written into a new part on storage:
 
 ![compression block diagram](images/partitioning-01.png)

docs/en/cloud/security/cloud-authentication.md

@@ -116,7 +116,7 @@ ClickHouse Cloud also supports security assertion markup language (SAML) single
 Use the SHA256_hash method when [creating user accounts](/docs/en/sql-reference/statements/create/user.md) to secure passwords.
 
 **TIP:** Since users with less than administrative privileges cannot set their own password, ask the user to hash their password using a generator
-such as [this one](https://tools.keycdn.com/sha256-online-generator) before providing it to the admin to setup the account. Passwords should follow the [requirements](#establish-strong-passwords) listed above.
+such as [this one](https://tools.keycdn.com/sha256-online-generator) before providing it to the admin to setup the account. Passwords should follow the [requirements](#password-settings) listed above.
 
 ```
 CREATE USER userName IDENTIFIED WITH sha256_hash BY 'hash';

docs/en/cloud/security/gcp-private-service-connect.md

@@ -108,7 +108,7 @@ In the Google Cloud console, navigate to **Network services -> Private Service C
 Open the Private Service Connect creation dialog by clicking on the **Connect Endpoint** button.
 
 - **Target**: use **Published service**
-- **Target service**: use **endpointServiceId** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-for-private-service-connect) step.
+- **Target service**: use **endpointServiceId** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step.
 - **Endpoint name**: set a name for the PSC **Endpoint name**.
 - **Network/Subnetwork/IP address**: Choose the network you want to use for the connection. You will need to create an IP address or use an existing one for the Private Service Connect endpoint. In our example, we precreated an address with the name **your-ip-address** and assigned IP address `10.128.0.2`
 - To make the endpoint available from any region, you can enable the **Enable global access** checkbox.