diff --git a/styles/elements/_inputs.scss b/styles/elements/_inputs.scss
index 16dd4fce..e7e01cf7 100644
--- a/styles/elements/_inputs.scss
+++ b/styles/elements/_inputs.scss
@@ -220,6 +220,7 @@
     &--anything,
     &--portfolioName,
     &--requiredField,
+    &--taskOrderNumber,
     &--email {
       input {
         max-width: 30em;
diff --git a/styles/sections/_task_order.scss b/styles/sections/_task_order.scss
index f031d317..78111fd9 100644
--- a/styles/sections/_task_order.scss
+++ b/styles/sections/_task_order.scss
@@ -68,6 +68,11 @@
     background-color: $color-gray-lightest;
   }
 
+  .usa-input__title,
+  .usa-input__title-inline {
+    font-weight: $font-normal;
+  }
+
   &.task_order__form {
     hr {
       margin-top: 1.5rem;
@@ -88,11 +93,6 @@
       max-width: unset;
     }
 
-    .usa-input__title,
-    .usa-input__title-inline {
-      font-weight: $font-normal;
-    }
-
     .date-picker {
       .usa-input__title {
         font-weight: $font-bold;
diff --git a/templates/task_orders/step_2.html b/templates/task_orders/step_2.html
index ac270e36..369bc590 100644
--- a/templates/task_orders/step_2.html
+++ b/templates/task_orders/step_2.html
@@ -9,6 +9,6 @@
 {% set step = "2" %}
 
 {% block to_builder_form_field %}
-  {{ TOFormStepHeader('task_orders.form.add_to_header' | translate, "Lorem ipsem")}}
+  {{ TOFormStepHeader('task_orders.form.add_to_header' | translate, 'task_orders.form.add_to_description' | translate)}}
   {{ TextInput(form.number, validation='taskOrderNumber', optional=False) }}
 {% endblock %}
diff --git a/translations.yaml b/translations.yaml
index 97e2816e..16a46cb0 100644
--- a/translations.yaml
+++ b/translations.yaml
@@ -172,7 +172,7 @@ forms:
       'no': 'No, not planning to develop natively in the cloud'
       not_sure: 'Not sure, unsure if planning to develop natively in the cloud'
       not_sure_help: Not sure? Talk to your technical lead about where and how they plan on developing your application.
-    number_description: Task order number (13 digit number from your system of record)
+    number_description: Task order number (13 digits)
     scope_description: 'What do you plan to do on the cloud? Some examples might include migrating an existing application or creating a prototype. You don’t need to include a detailed plan of execution, but should list key requirements. This section will be reviewed by your contracting officer, but won’t be sent to the CCPO. <p>Not sure how to describe your scope? <a href="#">Read some examples</a> to get some inspiration.</p>'
     scope_label: Cloud project scope
     start_date_label: Start of period of performance (PoP)
@@ -339,6 +339,7 @@ task_orders:
     add_clin: Add another CLIN or Sub-CLIN
     add_loa: Add another line of accounting
     add_to_header: Add your task order
+    add_to_description: Now, refer to your document to find the 13-digit task order number. It should be located at lorem ipsum dolar. From now on we'll refer to this portion of funding by the recorded task order number.
     base_clin_title: Add Base CLIN
     base_clin_description: Next, continue to refer to your document to locate your CLINs (Contract Line Item Numbers). CLINs are how you break the contract down by the commodities being procured (labor hours of services, funding for travel, quantity product A, etc.).
     clin_number_label: CLIN