Fix typo in PEP 625 email (#17120)

* Fix typo

* Put filename in quotes

Author: di

warehouse/templates/email/pep625-extension-email/body.html

@@ -28,7 +28,7 @@
     as-is and do not need to be updated.
   </p>
   <p>
-    Specifically, your recent upload of {{ filename }} is incompatible with PEP
+    Specifically, your recent upload of '{{ filename }}' is incompatible with PEP
     625 because it uses the .zip file extension.
   </p>
   <p>

warehouse/templates/email/pep625-extension-email/body.txt

@@ -19,7 +19,7 @@ This email is notifying you of an upcoming deprecation that we have determined m
 
 In the future, PyPI will require all newly uploaded source distribution filenames to comply with PEP 625 (https://peps.python.org/pep-0625/). Any source distributions already uploaded will remain in place as-is and do not need to be updated.
 
-Specifically, your recent upload of {{ filename }} is incompatible with PEP 625 because it uses the .zip extension.
+Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it uses the .zip extension.
 
 In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
 

warehouse/templates/email/pep625-name-email/body.html

@@ -28,8 +28,8 @@
     as-is and do not need to be updated.
   </p>
   <p>
-    Specifically, your recent upload of {{ filename }} is incompatible with PEP
-    625 because it does not contains the normalized project name
+    Specifically, your recent upload of '{{ filename }}' is incompatible with PEP
+    625 because it does not contain the normalized project name
     '{{ normalized_name }}'.
   </p>
   <p>

warehouse/templates/email/pep625-name-email/body.txt

@@ -19,7 +19,7 @@ This email is notifying you of an upcoming deprecation that we have determined m
 
 In the future, PyPI will require all newly uploaded source distribution filenames to comply with PEP 625 (https://peps.python.org/pep-0625/). Any source distributions already uploaded will remain in place as-is and do not need to be updated.
 
-Specifically, your recent upload of {{ filename }} is incompatible with PEP 625 because it does not contain the normalized project name '{{ normalized_name }}'.
+Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it does not contain the normalized project name '{{ normalized_name }}'.
 
 In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
 

warehouse/templates/email/pep625-version-email/body.html

@@ -28,7 +28,7 @@
     as-is and do not need to be updated.
   </p>
   <p>
-    Specifically, your recent upload of {{ filename }} is incompatible with PEP
+    Specifically, your recent upload of '{{ filename }}' is incompatible with PEP
     625 because it does not contain the normalized project version
     '{{ normalized_version }}'.
   </p>

warehouse/templates/email/pep625-version-email/body.txt

@@ -19,7 +19,7 @@ This email is notifying you of an upcoming deprecation that we have determined m
 
 In the future, PyPI will require all newly uploaded source distribution filenames to comply with PEP 625 (https://peps.python.org/pep-0625/). Any source distributions already uploaded will remain in place as-is and do not need to be updated.
 
-Specifically, your recent upload of {{ filename }} is incompatible with PEP 625 because it does not contain contain the normalized project version '{{ normalized_version }}'.
+Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it does not contain contain the normalized project version '{{ normalized_version }}'.
 
 In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.