fix: wording

oasisprotocol · Dec 6, 2024 · 4a34175 · 4a34175
1 parent c8ec358
commit 4a34175
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/docs/dapp/README.mdx b/docs/dapp/README.mdx
@@ -13,10 +13,10 @@ import {findSidebarItem} from '@site/src/sidebarUtils';
 The [Oasis architecture] is designed to have a simple, robust consensus layer
 on top which connects handful of ParaTimes executing smart contracts.
 
-[Sapphire] is the main ParaTime, which is EVM-compatible and let's you write
-confidential, as well as non-confidential smart contracts.
+[Sapphire] is the primary ParaTime. It is EVM-compatible and allows you to
+write both confidential and non-confidential smart contracts.
 
-An oveview of the other Paratimes, you can find the [Other ParaTimes] chapter.
+For an overview of the other ParaTimes, refer to the [Other ParaTimes] chapter.
 
 [Oasis architecture]: ../general/oasis-network/README.mdx
 [Sapphire]: /dapp/sapphire/README.mdx

diff --git a/docs/dapp/tools/other-paratimes/README.mdx b/docs/dapp/tools/other-paratimes/README.mdx
@@ -7,10 +7,10 @@ import {findSidebarItem} from '@site/src/sidebarUtils';
 
 # Other ParaTimes
 
-Beside our main ParaTime [Sapphire], there are a handful of other Paratimes
+In addition to our primary ParaTime, [Sapphire], several other ParaTimes are
 running on top of the consensus layer.
-DApp developers may choose among those ParaTimes depending on whether they
-require confidentiality and/or EVM-compatibility.
+DApp developers can build on these ParaTimes based on their specific
+requirements, such as confidentiality and EVM compatibility.
 
 Learn more by exploring the ParaTimes below!