Cleanup: Grammar: Fix uses of "for e.g."

e.g. stands for "exempli gratia" in Latin which means "for example".
The best way to make sure it makes sense when writing is to just expand
it to "for example". In these cases where the text was "for e.g.", that
leaves us with "for for example" which makes no sense. This commit fixes
all 110 cases, mostly just just replacing the words with "for example",
but also restructuring the text a bit more in a few cases, mostly by
moving "e.g." to the beginning of a list in parentheses.

Pull Request: https://projects.blender.org/blender/blender/pulls/139596

scripts/modules/_bpy_internal/extensions/stale_file_manager.py

@@ -162,7 +162,7 @@ class StaleFiles:
                 #
                 # If this ever did happen besides potentially trying to remove `base_directory`,
                 # this path could be treated as a file which could not be removed and queued for
-                # removal again causing a single space (for e.g.) to be left in the stale file,
+                # removal again causing a single space (for example) to be left in the stale file,
                 # trying to be removed every startup and failing.
                 # Avoid all these issues by checking the path doesn't resolve to being the same path as it's parent.
                 is_same = False

scripts/modules/_bpy_internal/extensions/wheel_manager.py

@@ -464,7 +464,7 @@ def wheel_version_from_filename_for_cmp(
     so comparing the first 3 numbers is sufficient. The trailing string is just a tie breaker in the
     unlikely event it differs.
 
-    If supporting the full spec, comparing: "1.1.dev6" with "1.1.6rc6" for e.g.
+    If supporting the full spec, comparing: "1.1.dev6" with "1.1.6rc6" for example
     we could support this doesn't seem especially important as extensions should use major releases.
     """
     filename_split = filename.split("-")

scripts/modules/addon_utils.py

@@ -1119,7 +1119,7 @@ def _initialize_extensions_compat_ensure_up_to_date(extensions_directory, extens
 
     if cache_data is not None:
         # NOTE: the exception handling here is fairly paranoid and accounts for invalid values in the loaded cache.
-        # An example would be values expected to be lists/dictionaries being other types (None or strings for e.g.).
+        # An example would be values expected to be lists/dictionaries being other types (None or strings for example).
         # While this should not happen, some bad value should not prevent Blender from loading properly,
         # so report the error and regenerate cache.
         try:

scripts/modules/rna_info.py

@@ -711,7 +711,7 @@ def BuildRNAInfo():
                 print("rna_info.BuildRNAInfo(..): ignoring type", repr(rna_type_name))
 
         # Now, there are some sub-classes in add-ons we also want to include.
-        # Cycles for e.g. these are referenced from the Scene, but not part of
+        # Cycles for example. These are referenced from the Scene, but not part of
         # bpy.types module.
         # Include all sub-classes we didn't already get from 'bpy.types'.
         i = 0

scripts/modules/rna_xml.py

@@ -239,7 +239,7 @@ def rna2xml(
 # paths "escaping" the intended data types, potentially writing into unexpected settings.
 # This is done because the XML itself defines the attributes which are recursed into,
 # there is a possibility the XML recurse into data that isn't logically owned by "root",
-# out of the theme and into user preferences for e.g. which could change trust settings
+# out of the theme and into user preferences for example, which could change trust settings
 # even executing code.
 #
 # At the time of writing it seems this is not possible with themes (the main user of this functionality),