Truncate two blogposts

blog/aurora-relayer-2-0.md

@@ -10,6 +10,8 @@ In the blockchain world, relayers are off-chain facilitators of data exchange an
 
 Initially developed in-house at NEAR, the Aurora EVM is the official EVM for the NEAR ecosystem. Powered by the SputnikVM, it accomplishes a 1:1 experience with the Ethereum protocol. This compatibility between Aurora and Ethereum is achieved by the **Aurora Relayer, **a** **JSON-RPC compatible server with Ethereum's [Web3 API](https://eth.wiki/json-rpc/API) for the [Aurora Engine. ](https://github.com/aurora-is-near/aurora-engine)It has its own internal database to serve multiple read methods and an indexer that is constantly following the head and indexing blocks, transactions and logs to that internal database
 
+<!-- truncate -->
+
 ### **Relayer 2.0**
 
 As mentioned above, the Aurora Relayer has two main components. First, an implementation of Ethereum’s JSON-RPC specification—a standard collection of methods that all clients must implement and the canonical interface between users and the Ethereum network—on Aurora’s Ethereum Virtual Machine (EVM), a.k.a. the Aurora Engine. Second, an indexer that continuously reads the NEAR network for blocks and other relevant information relevant to Aurora. 

blog/communication-from-aurora-to-near-local-testing.md

@@ -15,6 +15,8 @@ In this article, we will learn how to write local tests for the Aurora contracts
 
 The example described in this article: [https://github.com/olga24912/AuroraToNearXCCExample](https://github.com/olga24912/AuroraToNearXCCExample)
 
+<!-- truncate -->
+
 ## Counter contract on Near
 
 I assume that you have already cloned a git repo locally or just created your own repo, in the case you want to add everything file by file to your project using this article.