summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVictor Wu <wu.victor@gmail.com>2016-11-16 23:16:14 +0000
committerVictor Wu <wu.victor@gmail.com>2016-11-16 23:16:14 +0000
commitc4f5883df509241b814eca2d58fee40669833e1b (patch)
treee1ea7628e36fbc61d10cfc478c05cd171ba254e5
parentcbf02a266fafab91d3c5bf6e4599267a2f9b0836 (diff)
downloadgitlab-ce-copy-guidelines-merge-requests.tar.gz
-rw-r--r--doc/development/ux_guide/copy.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/ux_guide/copy.md b/doc/development/ux_guide/copy.md
index f1e452e1572..0fb193a83cf 100644
--- a/doc/development/ux_guide/copy.md
+++ b/doc/development/ux_guide/copy.md
@@ -59,7 +59,7 @@ Use `5 open issues` and don't use `5 pending issues`.
| Re-open | Re-open a closed issue | There should never be a need to use `open` as a verb |
| Delete | Delete an open or closed issue ||
-#### Add item
+#### Add issue
When viewing a list of issues, there is a button that is labeled `Add`. Given the context in the example, it is clearly referring to issues. If the context were not clear enough, the label could be `Add issue`. Clicking the button will bring you to the `Add issue` form. Other add flows should be similar.
@@ -69,7 +69,7 @@ The form should be titled `Add issue`. The submit button should be labeled `Subm
![Add issue form](img/copy-form-addissueform.png)
-#### Edit item
+#### Edit issue
When in context of an issue, the affordance to edit it is labeled `Edit`. If the context is not clear enough, `Edit issue` could be considered. Other edit flows should be similar.