[clang] Fix typo in "translation unit" in analyzer doc CommandLineUsage.rst (PR #112966)

[via cfe-commits]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang-static-analyzer-1

Author: BrnBlrg (BenBlumer)

<details>
<summary>Changes</summary>

Fix typo in "translation unit" in analyzer doc CommandLineUsage.rst

---
Full diff: https://github.com/llvm/llvm-project/pull/112966.diff


1 Files Affected:

- (modified) clang/docs/analyzer/user-docs/CommandLineUsage.rst (+1-1) 


``````````diff
diff --git a/clang/docs/analyzer/user-docs/CommandLineUsage.rst b/clang/docs/analyzer/user-docs/CommandLineUsage.rst
index d7f8253469df40..59f8187f374a95 100644
--- a/clang/docs/analyzer/user-docs/CommandLineUsage.rst
+++ b/clang/docs/analyzer/user-docs/CommandLineUsage.rst
@@ -2,7 +2,7 @@ Command Line Usage: scan-build and CodeChecker
 ==============================================
 
 This document provides guidelines for running the static analyzer from the command line on whole projects.
-CodeChecker and scan-build are two CLI tools for using CSA on multiple files (tranlation units).
+CodeChecker and scan-build are two CLI tools for using CSA on multiple files (translation units).
 Both provide a way of driving the analyzer, detecting compilation flags, and generating reports.
 CodeChecker is more actively maintained, provides heuristics for working with multiple versions of popular compilers and it also comes with a web-based GUI for viewing, filtering, categorizing and suppressing the results.
 Therefore CodeChecker is recommended in case you need any of the above features or just more customizability in general.

``````````

</details>


https://github.com/llvm/llvm-project/pull/112966