Typo fix in new_request_agency.html and added DCP blue box

app/request/api/views.py

@@ -236,7 +236,7 @@ def get_request_responses():
 
     else:
         # If the user is not an agency user assigned to the request or the requester, then only responses that are
-        # "Release and Public" whose release date is not in the future can b e retrieved.
+        # "Release and Public" whose release date is not in the future can be retrieved.
         responses = Responses.query.filter(
             Responses.request_id == current_request.id,
             ~Responses.id.in_([cm.method_id for cm in CommunicationMethods.query.all()]),

app/templates/request/new_request_agency.html

@@ -131,7 +131,7 @@ <h1>Alternate Contact Information
                 </h1>
 
                 <p>No information entered in this section will be visible to the public.</p>
-                <p>Note: You must have provide at least one type of contact information (phone number, fax number, or
+                <p>Note: You must provide at least one type of contact information (phone number, fax number, or
                     address)</p>
                 {# User of title #}
                 {{ form.user_title.label(class="request-heading") }}

data/agencies.json

@@ -548,7 +548,7 @@
           "generate_letters": false
         },
         "specific_request_instructions": {
-          "text": ""
+          "text": "<strong>In the “Request Description” box, please describe with as much specificity as possible the record(s) you are requesting.  Include, as applicable, the following information:</strong><br /><i><ul><li>Project name</li><li>Address</li><li>Borough(s)</li><li>Block numbers(s)</li><li>Lot number(s)</li><li>CP or ULURP number(s)</li><li>CEQR number(s)</li><li>Relevant dates</li><li>Type of record(s)</li></ul></i><strong>Please note: </strong>Broadly worded requests seeking “any” or “all” records related to a subject matter have the potential to implicate hundreds if not thousands of records, including emails. Requests for emails require an extensive search, and a determination regarding such a broad request typically takes a minimum of sixty (60) business days. If making a request for emails, when possible, the specific sender(s) and recipient(s) should be identified, as well as specific date ranges.<br /><br />See more information about the <a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https://www1.nyc.gov/assets/planning/download/pdf/about/proc_pub_inspection.pdf?r=0518\">Department's FOIL procedures</a>."
         }
       }
     },

data/agencies_test.json

@@ -548,7 +548,7 @@
           "generate_letters": false
         },
         "specific_request_instructions": {
-          "text": ""
+          "text": "<strong>In the “Request Description” box, please describe with as much specificity as possible the record(s) you are requesting.  Include, as applicable, the following information:</strong><br /><i><ul><li>Project name</li><li>Address</li><li>Borough(s)</li><li>Block numbers(s)</li><li>Lot number(s)</li><li>CP or ULURP number(s)</li><li>CEQR number(s)</li><li>Relevant dates</li><li>Type of record(s)</li></ul></i><strong>Please note: </strong>Broadly worded requests seeking “any” or “all” records related to a subject matter have the potential to implicate hundreds if not thousands of records, including emails. Requests for emails require an extensive search, and a determination regarding such a broad request typically takes a minimum of sixty (60) business days. If making a request for emails, when possible, the specific sender(s) and recipient(s) should be identified, as well as specific date ranges.<br /><br />See more information about the <a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https://www1.nyc.gov/assets/planning/download/pdf/about/proc_pub_inspection.pdf?r=0518\">Department's FOIL procedures</a>."
         }
       }
     },