Update threat_intelligence.md

[carlostomas-dd]

What does this PR do? What is the motivation?

There is a typo in the Threat Intel categories documentation. It's not Tor but tor (lowercase)

We can see there are no spans with category Tor but there are a few with tor

Same happens with logs, none with Tor but many with tor

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

[brett0000FF]

@carlostomas-dd - Thanks for making this update! Would you be able to re-open a new PR and name your branch with the <username>/<branch name> format? Otherwise, this blocks our merge queue. Also, no need to update the Japanese docs. This change will propagate through our translation pipeline (no harm having it--it'll just get overwritten).

Let me know if you'd like any help. Thanks!

[michaelcretzman]

@carlostomas-dd I went ahead and discarded the changes to the Japanese files as these will get overwritten during translation.
I'm going to merge this PR because it contain a tiny change.

In the future, please use the <Slack username>/<branch name> format for branches. Otherwise, our merge queue is blocked and we can't merge your PR w/o overriding the requirements.