From 40f20c1cdec0b46683f46e2534d137636bc4dba4 Mon Sep 17 00:00:00 2001 From: Ivo Anjo Date: Mon, 22 Aug 2022 13:35:03 +0100 Subject: [PATCH] Fix outdated references to `use` instead of `instrument` in docs While reviewing #2217 where we fixed the sinatra documentation not to mention the outdated `use`, I decided to make a quick check if we had any more such leftovers, and it turns out we did. This PR fixes the two leftover mentions of `use` that I found that should be replaced by `instrument`. I did not change the sinatra docs to avoid a conflict with #2217. --- docs/GettingStarted.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md index cd33b344f0e..9fd6cc18f47 100644 --- a/docs/GettingStarted.md +++ b/docs/GettingStarted.md @@ -1063,7 +1063,7 @@ end YourSchema.execute(query, variables: {}, context: {}, operation_name: nil) ``` -The `use :graphql` method accepts the following parameters. Additional options can be substituted in for `options`: +The `instrument :graphql` method accepts the following parameters. Additional options can be substituted in for `options`: | Key | Description | Default | | --- | ----------- | ------- | @@ -1116,7 +1116,7 @@ YourSchema.define do end ``` -Do *NOT* `use :graphql` in `Datadog.configure` if you choose to configure manually, as to avoid double tracing. These two means of configuring GraphQL tracing are considered mutually exclusive. +Do *NOT* `instrument :graphql` in `Datadog.configure` if you choose to configure manually, as to avoid double tracing. These two means of configuring GraphQL tracing are considered mutually exclusive. ### gRPC