[DOCS] Removed inconsistency in clang vs Clang usage in docs (c vs C)

[sushmaunnibhavi]

Summary

Fixed bug #37411
Bug Link:https://bugs.llvm.org/show_bug.cgi?id=37411

[xgupta]

LGTM, Thanks for the patch!

[jrtc27]

I'm not convinced by these changes?

[xgupta]

In D101352#2726406, @jrtc27 wrote:

I'm not convinced by these changes?

Yes, I also thought first, clang man page can't be incorrect/inconsistent.
I think @rnk can suggest the changes as he has also commented on the Bugzilla issue.
(I also got confused in Clang vs clang naming, sorry if I accepted revision with not much thought)

[rnk]

This is what I said back in 2018 on the bug:

I think you're right, we generally try to capitalize "Clang" when referring to the project and use lower case when talking about the command name. People do the same thing with "GCC" and "gcc". We're not always consistent though. Patches welcome I guess.

I think most of the instances in this patch should stay capitalized. Some of them are ambiguous, they could be referring to Clang the product, or clang the command. In the face of ambiguity, I think more capitalization is better.

[rnk]

I should add that I started to think this way after @chandlerc asked me to capitalize "Clang" in some slides for a presentation I was giving years ago. I didn't invent this convention, other people already follow it.

[xgupta]

@sushmaunnibhavi Please close this revision, I got some misunderstading. Changes are not expected here.

[sushmaunnibhavi]

In D101352#2739003, @xgupta wrote:

@sushmaunnibhavi Please close this revision, I got some misunderstading. Changes are not expected here.

Yes, will do it.

clang/docs/CommandGuide/clang.rst

 clang - the Clang C, C++, and Objective-C compiler
 ==================================================
 
 SYNOPSIS
 --------
 
 :program:`clang` [*options*] *filename ...*
 
 DESCRIPTION
 -----------
 
 :program:`clang` is a C, C++, and Objective-C compiler which encompasses
 preprocessing, parsing, optimization, code generation, assembly, and linking.
-Depending on which high-level mode setting is passed, Clang will stop before
+Depending on which high-level mode setting is passed, clang will stop before
 doing a full link.  While Clang is highly integrated, it is important to
 understand the stages of compilation, to understand how to invoke it.  These
 stages are:
 
 Driver
     The clang executable is actually a small driver which controls the overall
     execution of other tools such as the compiler, assembler and linker.
     Typically you do not need to interact with the driver, but you
.. option:: --print-supported-cpus
   target is specified, the system default target will be used.
 
 .. option:: -mcpu=?, -mtune=?
 
   Acts as an alias for :option:`--print-supported-cpus`.
 
 .. option:: -march=<cpu>
 
-  Specify that Clang should generate code for a specific processor family
+  Specify that clang should generate code for a specific processor family
   member and later.  For example, if you specify -march=i486, the compiler is
   allowed to generate instructions that are valid on i486 and later processors,
   but which may not exist on earlier ones.
 
 
 Code Generation Options
 ~~~~~~~~~~~~~~~~~~~~~~~
 
Specify which optimization level to use:
     :option:`-O` Equivalent to :option:`-O1`.
 
     :option:`-O4` and higher
 
       Currently equivalent to :option:`-O3`
 
 .. option:: -g, -gline-tables-only, -gmodules
 
-  Control debug information output.  Note that Clang debug information works
+  Control debug information output.  Note that clang debug information works
   best at :option:`-O0`.  When more than one option starting with `-g` is
   specified, the last one wins:
 
     :option:`-g` Generate debug information.
 
     :option:`-gline-tables-only` Generate only line table debug information. This
     allows for symbolicated backtraces with inlining information, but does not
     include any information about variables, their locations or types.
specified, the last one wins:
     references to the module cache on the machine the object files in the
     library were built on.
 
 .. option:: -fstandalone-debug -fno-standalone-debug
 
   Clang supports a number of optimizations to reduce the size of debug
   information in the binary. They work based on the assumption that the
   debug type information can be spread out over multiple compilation units.
-  For instance, Clang will not emit type definitions for types that are not
+  For instance, clang will not emit type definitions for types that are not
   needed by a module and could be replaced with a forward declaration.
-  Further, Clang will only emit type info for a dynamic C++ class in the
+  Further, clang will only emit type info for a dynamic C++ class in the
   module that contains the vtable for the class.
 
   The :option:`-fstandalone-debug` option turns off these optimizations.
   This is useful when working with 3rd-party libraries that don't come with
-  debug information.  This is the default on Darwin.  Note that Clang will
+  debug information.  This is the default on Darwin.  Note that clang will
   never emit type information for types that are not referenced at all by the
   program.
 
 .. option:: -feliminate-unused-debug-types
 
-  By default, Clang does not emit type information for types that are defined
+  By default, clang does not emit type information for types that are defined
   but not used in a program. To retain the debug info for these unused types,
   the negation **-fno-eliminate-unused-debug-types** can be used.
 
 .. option:: -fexceptions
 
   Enable generation of unwind information. This allows exceptions to be thrown
   through Clang compiled stack frames.  This is on by default in x86-64.
 
.. option:: -v
   Show commands to run and use verbose output.
 
 
 Diagnostics Options
 ~~~~~~~~~~~~~~~~~~~
 
 .. option:: -fshow-column, -fshow-source-location, -fcaret-diagnostics, -fdiagnostics-fixit-info, -fdiagnostics-parseable-fixits, -fdiagnostics-print-source-range-info, -fprint-source-range-info, -fdiagnostics-show-option, -fmessage-length
 
-  These options control how Clang prints out information about diagnostics
+  These options control how clang prints out information about diagnostics
   (errors and warnings). Please see the Clang User's Manual for more information.
 
 Preprocessor Options
 ~~~~~~~~~~~~~~~~~~~~
 
 .. option:: -D<macroname>=<value>
 
   Adds an implicit #define into the predefines buffer which is read before the