5
2 Comments

Native speakers, I need your help to improve these few lines of text.

Hey guys, recently I launched my side project AsyncTrace - https://www.asynctrace.com while showing some friends they said the site text could be improved, Can someone please help me to fix the wording? Here are the texts:

AsyncTrace Features

  1. Full stacktrace - We track all possible asynchronous functions. So no worries to lose some stacktrace.
  2. Clean stacktrace - We remove all the framework/vendor/3rd-party related stacktrace. Focus only on what you need.
  3. Better visibility - Two separate dashboards will increase visibility. A developer can see whatever they need to fix the bug and the Product owner can see the holistic view of the product.
  4. Focus on the component - We focus on components instead of files like which component, service or util class has a problem.
  5. Extra steps for Promise and template - We provide additional information besides stacktrace like header, status code, URL and template error details.
  6. Root cause - We provide event details, which help to understand why the change detection triggered.

Why should you use AsyncTrace?

  1. Save Time - Here at AsyncTrace, we provide full and clean stacktrace regardless of asynchronous/synchronous code. You don’t need to spend hours debugging to find the bug.
  2. Bug-free component - Traditional error trackers are still using file-focused bug reporting, here at AsyncTrace, we focus component. Component focus analysis highlights how many bugs are associated, so you can build bug-free components.
  3. Don’t repeat a bug - If you understand why change-detection triggered then you’ll understand the context of the bug, so you’ll avoid unnecessary null/undefined check.
  4. More than error tracking - AsyncTrace is not just an error tracker! AsyncTrace highlights the complexity of a bug, it highlights how the small components are entangled to each other, as a user you’ll understand how customers interact with your product.

Thanks in advance.

on February 3, 2020
  1. 3

    I pasted your text into this Gist and then edited it to sound more natural to my native ear.

    I don't have much Angular experience, so some of the terminology is a lost on me. But I think this improves the text and fixes some grammar issues. Hope it helps!

    1. 1

      Thank you very much, it is a great help :) I can fix the Angular related wording :)