Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #156 from christianbraeunlich/feature/correct-sentences

Browse source 
Correct sentences
This commit is contained in:
Jeremy Vyska 2022-03-25 16:08:58 +01:00 • committed by GitHub
commit 1653ec32cc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/docs/BestPractices/CustomTelemetry/index.md
View file

@ -71,7 +71,7 @@ Of course it is possible to have a single object as a central place to emit tele
## Candidate data for telemetry
Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database)
Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database).
Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data.

2
content/docs/BestPractices/api-page/index.md
View file

@ -166,7 +166,7 @@ It is common use to give certain fields a more describing name. Some examples ar
These fields should always be part of the API Page:
* SystemId
* This field should be exposed wit the name ```id```
* This field should be exposed with the name ```id```
* SystemModifiedAt
* This field should be exposed with the name ```lastModifiedDateTime```. If you choose a different name, then the webhook functionality will not work properly.