[tor-commits] [community/staging] Close quotes

[hiro@xxxxxxxxxxxxxx]

commit 1de0beb43c554aeac816d3d3bc85a908e90f3398
Author: null pointer exception <57326449+deathgrippin@xxxxxxxxxxxxxxxxxxxxxxxx>
Date:   Wed May 27 19:09:15 2020 +0000

    Close quotes
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 43c5592..591645f 100644
--- a/README.md
+++ b/README.md
@@ -90,7 +90,7 @@ This is the workflow that Tor Internal people should use when making changes on
     - Update "Title" with a short title to explain your changes.
     - Update "Description", you can use the commit message you entered before additionally referencing the original issue you have reviewed, e.g. `https://dip.torproject.org/web/community/issues/3`, and tagging one of the repo maintainers, e.g. `@pili`, so they know the change can be merged.
     - Make sure that both "Delete source branch when merge request is accepted" and "Squash commits when merge request is accepted" are checked.
-    - Click "Submit merge request.
+    - Click "Submit merge request".
 5. Reviewer should comment on the original issue with a link to the merge request created, e.g. `https://dip.torproject.org/steph/community/merge_requests/2`.
 
 ### Volunteer Workflow



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits