Fix build

Author: ihordiachenko

docs/commitment-trees/overview.mdx

@@ -12,13 +12,13 @@ Although Rarimo users fully own their confidential social graph, some on-chain s
 
 Rarimo Protocol defines the following tree types:
 - [Statement Trees(ST)](/commitment-trees/statement-trees) containing basic statements
-- [Credential Trees(CT)](/credential-trees) used for hierarchical one-to-many relations
+- Credential Trees(CT) used for hierarchical one-to-many relations
 - [Time Trees(TT)](/commitment-trees/time-trees) active for a specific time range
 
 <IdealImage img={require('/img/social-forest.png')} alt="Social forest" />
 
 An aggregation of commitment trees corresponding to some confidential social graph forms a social forest. The social forest can be used to build novel privacy-first social apps. Here are several examples of such applications:
 - Users seeking to create a permissionless chat may utilize the [Arbitrary Statement Tree(ARST)](/commitment-trees/statement-trees#arbitrary-statement-trees). Each message is encapsulated within a corresponding commitment. For anonymity, participants might opt for random salts and signatures, discarding them after usage. Deterministic salt and consistent keypairs for signing can be used to prove the message sequence later.
 - The [Adjustable Statement Tree(ADST)](/commitment-trees/statement-trees#adjastable-statement-trees)  can be employed to establish a chat accessible only to users meeting specific criteria. Users must provide proof of eligibility when posting messages, with the eligibility criteria set transparently by the chat's creator and enforced via smart contract.
-- Entities desiring to act as identity providers, such as authoritative organizations issuing verifiable credentials, should use the [Credential Trees](/credential-trees). Unlike the `ARST` and `ADST` trees, this tree type is exclusively manageable by its owner.
+- Entities desiring to act as identity providers, such as authoritative organizations issuing verifiable credentials, should use the Credential Trees. Unlike the `ARST` and `ADST` trees, this tree type is exclusively manageable by its owner.
 - The [Time Trees(TT)](/commitment-trees/time-trees) are most suitable for events confined to a specific timeframe, such as petition signings or periodic check-ins for liveness proofs.

docs/commitment-trees/time-trees.mdx

@@ -8,4 +8,4 @@ import IdealImage from '@site/src/components/IdealImage';
 
 # Time trees
 
-Time Trees are active within some time frame and restrict the addition of new commitments after a predetermined point. They can be implemented on top of both [statement trees](/commitment-trees/statement-trees) and [credential trees](/credential-trees).
+Time Trees are active within some time frame and restrict the addition of new commitments after a predetermined point. They can be implemented on top of both [statement trees](/commitment-trees/statement-trees) and credential trees.

docs/rarimo-core/overview.mdx

@@ -26,7 +26,6 @@ Oracles observe events in the outer world in a trustless way, and Validators col
 
 The protocol provides a general messaging protocol foundation for cross-chain use cases.
 Users can implement their own sub-protocols and submit them via the proposals mechanism.
-Rarimo offers ready-to-use [identity](/credential-trees) sub-protocol.
 
 <IdealImage img={require('/img/protocol-layers.png')} alt="Rarimo Protocols" />