@@ -282,12 +282,13 @@ If you would like to contribute to the SDK, go here for more information:
282282
283283### Support
284284
285- 1 . You will be granted support if you or your company are already covered
286- under an existing maintenance/support agreement. Send an email to
287- support@splunk.com _ and include "Splunk SDK for Python" in the subject line.
285+ 1 . You will be granted support if you or your company are already covered
286+ under an existing maintenance/support agreement.
287+ Send an email to support@splunk.com and include "Splunk SDK for Python"
288+ in the subject line.
2882892 . If you are not covered under an existing maintenance/support agreement, you
289290 can find help through the broader community at:
290- <ul >
291+ <ul >
291292 <li ><a href =' http://splunk-base.splunk.com/answers/ ' >Splunk Answers</a > (use
292293 the <b >sdk</b >, <b >java</b >, <b >python</b >, and <b >javascript</b > tags to
293294 identify your questions)</li >
@@ -298,9 +299,8 @@ If you would like to contribute to the SDK, go here for more information:
298299 code in the <b >/splunklib</b > directory) has been modified. If you modify an
299300 SDK and want support, you can find help through the broader community and
300301 Splunk answers (see above). We would also like to know why you modified the
301- core library&mdash ; please send feedback to _ devinfo@splunk.com _ .
302- 4 . File any issues on
303- [ GitHub] ( https://github.com/splunk/splunk-sdk-python/issues ) .
302+ core library&mdash ; please send feedback to devinfo@splunk.com .
303+ 4 . File any issues on [ GitHub] ( https://github.com/splunk/splunk-sdk-python/issues ) .
304304
305305### Contact Us
306306
0 commit comments