diff options
| author | Leonid Logvinov <logvinov.leon@gmail.com> | 2019-01-18 19:46:16 +0800 |
|---|---|---|
| committer | Leonid Logvinov <logvinov.leon@gmail.com> | 2019-01-18 19:46:16 +0800 |
| commit | e6fe728bcbbab0c500fc7adee1439505282e8eca (patch) | |
| tree | d7c4d43725b460776857ff421397d6c4b8c30603 /packages/dev-tools-pages/ts/components/trace.tsx | |
| parent | 6c7f4c13fa3de20c554e9c031f272d0f66842580 (diff) | |
| parent | bef30e4209b26c8d4f443f8672e9acb9471c6a37 (diff) | |
| download | dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar.gz dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar.bz2 dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar.lz dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar.xz dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.tar.zst dexon-sol-tools-e6fe728bcbbab0c500fc7adee1439505282e8eca.zip | |
Merge development
Diffstat (limited to 'packages/dev-tools-pages/ts/components/trace.tsx')
| -rw-r--r-- | packages/dev-tools-pages/ts/components/trace.tsx | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/packages/dev-tools-pages/ts/components/trace.tsx b/packages/dev-tools-pages/ts/components/trace.tsx index f41dac9b7..81f6db0ab 100644 --- a/packages/dev-tools-pages/ts/components/trace.tsx +++ b/packages/dev-tools-pages/ts/components/trace.tsx @@ -25,7 +25,7 @@ const Trace: React.StatelessComponent<{}> = () => ( troublemaking line of code. The only hint you'll get is a generic error. </MainCopy> <Breakout> - <Code isLight={true}>Error: VM Exception while processing transaction: rever</Code> + <Code isLight={true}>Error: VM Exception while processing transaction: revert</Code> </Breakout> <List> @@ -44,8 +44,8 @@ const Trace: React.StatelessComponent<{}> = () => ( <Copy dark={true}> <Gamma as="h3">Time-consuming</Gamma> <p> - Working with a large code-base that contains hundreds of smart contracts, - finding the failing line of code quickly becomes a daunting task. + Working within a large code-base that contains many smart contracts, finding the + failing line of code quickly becomes a daunting task. </p> </Copy> <Icon as={TimeConsuming} /> @@ -78,8 +78,8 @@ const Trace: React.StatelessComponent<{}> = () => ( <Copy> <Gamma as="h3">Exact location</Gamma> <p> - It shows you the exact location of the specific code linen and where it was - called from. + It shows you the exact location of the offending line and where it was called + from. </p> </Copy> <Icon as={ExactLocation} /> @@ -90,8 +90,7 @@ const Trace: React.StatelessComponent<{}> = () => ( <Gamma as="h3">Time-saving</Gamma> <p> Turning "Your code failed somewhere, good luck debugging it" into "Your code - failed on line X of contract Y", it drastically improves the developer - experience. + failed on line X of contract Y", drastically improves the developer experience. </p> </Copy> <Icon as={TimeSaving} /> |