Clarified that HTTP headers are optional

Luis Cabrera · web-flow · commit 052f3823dfe6 · 2020-01-15T14:29:14.000-08:00
HTTP headers are really just a extra knob for the user, not a requirement.
diff --git a/articles/search/cognitive-search-custom-skill-interface.md b/articles/search/cognitive-search-custom-skill-interface.md
@@ -118,7 +118,7 @@ As shown in the previous example, you may return error and warning messages for
 
 ## Consuming custom skills from skillset
 
-When you create a Web API enricher, you can describe HTTP headers and parameters as part of the request. The snippet below shows how request parameters and HTTP headers may be described as part of the skillset definition.
+When you create a Web API enricher, you can describe HTTP headers and parameters as part of the request. The snippet below shows how request parameters and *optional* HTTP headers may be described as part of the skillset definition. HTTP headers are not a requirement, but they allow you to add additional configuration capabilities to your skill and to set them from the skillset definition.
 
 ```json
 {

Original file line number	Diff line number	Diff line change
`@@ -118,7 +118,7 @@ As shown in the previous example, you may return error and warning messages for`
`118`	`118`
`119`	`119`	`## Consuming custom skills from skillset`
`120`	`120`
`121`		`-When you create a Web API enricher, you can describe HTTP headers and parameters as part of the request. The snippet below shows how request parameters and HTTP headers may be described as part of the skillset definition.`
	`121`	`+When you create a Web API enricher, you can describe HTTP headers and parameters as part of the request. The snippet below shows how request parameters and optional HTTP headers may be described as part of the skillset definition. HTTP headers are not a requirement, but they allow you to add additional configuration capabilities to your skill and to set them from the skillset definition.`
`122`	`122`
`123`	`123`	```json
`124`	`124`	`{`