Skip to content

Commit a22e041

Browse files
Apply suggestions from code review
Co-authored-by: rchinn-segment <[email protected]>
1 parent 319de2f commit a22e041

File tree

1 file changed

+6
-6
lines changed
  • src/connections/destinations/catalog/avo

1 file changed

+6
-6
lines changed

src/connections/destinations/catalog/avo/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ beta: true
55
redirect_from: "/connections/destinations/catalog/actions-avo/"
66
---
77

8-
**Avo lets you find, fix, and prevent data quality issues upstream.** World class data and product teams at companies like Fender, IKEA, Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.
8+
**Avo lets you find, fix, and prevent data quality issues upstream.** World class data and product teams at companies like Fender, IKEA, and Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.
99

1010
With [Avo](https://avo.app){:target="\_blank”} Inspector, data quality is no longer a dream, it’s a workflow.
1111
[Inspector](https://www.avo.app/data-observability){:target="\_blank”} lets you find, triage, fix, and prevent data quality issues in your event based data. Launch Inspector to discover all your data quality issues and systematically work towards better data, one resolved issue at a time.
@@ -51,9 +51,9 @@ This Track call is translated into an event signature that is sent to Avo's Insp
5151
4. Select a source to connect to Avo (Actions) and click **Next**.
5252
5. Enter a name for your Avo (Actions) destination and click **Create destination**.
5353

54-
## Configure Avo Setup
54+
## Configure Avo
5555

56-
### Getting Avo API key
56+
### Get the Avo API key
5757

5858
Before connecting the Segment source to Avo, you will need an API key for your source.
5959

@@ -67,7 +67,7 @@ Before connecting the Segment source to Avo, you will need an API key for your s
6767

6868
### Configure Destination
6969

70-
#### Avo Inspector API Key
70+
#### Avo Inspector API key
7171

7272
You can copy the API key from your source in Avo. The API key allows Avo to map the events from your Segment source to the Avo source, to accurately compare your source’s event schemas to your Tracking Plan in Avo.
7373

@@ -78,11 +78,11 @@ Avo only generates issues for events in your `Production` environment, but you c
7878

7979
#### App Version Property
8080

81-
App Version Property is an optional **(but recommended!)** field. Having accurate app release versions in Avo Inspector allows you to see how events change across releases. This helps you identify which releases an issue is impacting, and monitor for regressions in future releases after an issue has been resolved.
81+
App Version Property is an optional **(but recommended)** field. Having accurate app release versions in Avo Inspector allows you to see how events change across releases. This helps you identify which releases an issue is impacting, and monitor for regressions in future releases after an issue has been resolved.
8282

8383
Without app versions, the inspector has no way of differentiating between old and new releases, and might surface irrelevant issues based on old releases. Learn more about how Inspector uses releases in [Avo's documentation](https://www.avo.app/docs/inspector/inspector-issues-view#release-and-source-breakdown){:target="\_blank”}.
8484

85-
For most mobile sources, Avo automatically fetches the app version from Segment Context. If you have an event property describing the app release version of your source (“E.g “app_version”) you can provide it under App Version.
85+
For most mobile sources, Avo automatically fetches the app version from Segment Context. If you have an event property describing the app release version of your source (for example, “app_version”) you can provide it under App Version.
8686

8787
If you are unsure of whether this applies to your source, or if you don’t know which event property to use, you can proceed with setting up the source and add this information later.
8888

0 commit comments

Comments
 (0)