Skip to content

Commit cc73d33

Browse files
committed
typo
1 parent 71872b4 commit cc73d33

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -222,11 +222,11 @@ When no service call is being traced, the custom request attributes are dropped.
222222

223223
<a name="webrequests"/>
224224

225-
## Trace web requests
225+
### Trace web requests
226226

227227
<a name="inwebrequests"/>
228228

229-
### Trace incoming web requests
229+
#### Trace incoming web requests
230230

231231
You can use the SDK to trace incoming web requests. This might be useful if Dynatrace does not support the respective web server framework or language processing the incoming web requests.
232232

@@ -236,7 +236,7 @@ To trace an incoming web request you first need to create a WebServerInfo object
236236
WebServerInfo wsInfo = OneAgentSDK.createWebServerInfo("WebShopProduction", "CheckoutService", "/api/service/checkout");
237237
```
238238

239-
To trace a specific incoming web request you then need to create a Tracer object. Make sure you provide all http headers from the request to the SDK by calling addRequestHeader(...). This ensures that tagging with our built-in sensor is working.
239+
To trace a specific incoming web request you then need to create a Tracer object. Make sure you provide all http headers from the request to the SDK by calling addRequestHeader(...). This ensures that tagging with our built-in sensor will work.
240240

241241
```Java
242242
IncomingWebRequestTracer tracer = OneAgentSDK.traceIncomingWebRequest(wsInfo,"https://www.oursupershop.com/api/service/checkout/save","POST")
@@ -258,7 +258,7 @@ try {
258258
int statusCodeReturnedToClient = processWebRequest();
259259
tracer.setStatusCode(statusCodeReturnedToClient);
260260
} catch (Exception e) {
261-
tracer.setStatusCode(500); // we expect, the container sends http 500 in case request processing throws an exception
261+
tracer.setStatusCode(500); // we expect that the container sends HTTP 500 status code in case request processing throws an exception
262262
tracer.error(e);
263263
throw e;
264264
} finally {
@@ -268,11 +268,11 @@ try {
268268

269269
<a name="outwebrequests"/>
270270

271-
### Trace outgoing web requests
271+
#### Trace outgoing web requests
272272

273-
You can use the SDK to trace outgoing web requests. This might be useful if Dynatrace does not support the respective http library or language.
273+
You can use the SDK to trace outgoing web requests. This might be useful if Dynatrace does not support the respective http library or language sending the request.
274274

275-
To trace a outgoing web request you need to create a Tracer object. It is important to send the Dynatrace Header. This ensures that tagging with our built-in sensor is working.
275+
To trace an outgoing web request you need to create a Tracer object. It is important to send the Dynatrace Header. This ensures that tagging with our built-in sensor will work.
276276

277277
```Java
278278
OutgoingWebRequestTracer outgoingWebRequestTracer = oneAgentSdk.traceOutgoingWebRequest(url, "GET");

0 commit comments

Comments
 (0)