diff --git a/Submitting-useful-bug-reports.md b/Submitting-useful-bug-reports.md
index d240772..ac9da4f 100644
--- a/Submitting-useful-bug-reports.md
+++ b/Submitting-useful-bug-reports.md
@@ -68,7 +68,7 @@ Debug log is like a history which tells what Signal was doing while it was runni
 Note: If you are using a passphrase and the bug appears before you can successfully unlock the app you can capture a debug log directly via the menu in the passphrase screen. If you cannot access any of Signal's debug log menus please see [how to capture debug logs with `adb`](#debug-logs-with-adb) below.
 
 #### Debug log privacy
-Debug logs captured within Signal are stripped from personal information. However please note that the last two digits of your and your contacts phone numbers may be visible in the logs. E.g. `+1 555 3455` will show as `+******55` in the log. This is to help differentiate the contacts when analysing a log.
+Debug logs captured within Signal are stripped from personal information. However please note that the last three digits of your and your contacts phone numbers may be visible in the logs. E.g. `+1 555 34557` will show as `+******557` in the log. This is to help differentiate the contacts when analysing a log.
 
 ### Add a screenshot
 Sometimes a picture is worth a thousand lines of debug logs (this doesn't mean that you shouldn't add a debug log too :). If the problem is visual and difficult to describe a screenshot can come a long way. Different Android vendors have different ways of taking screenshots. Please check how to do it on your specific device. Usually it's a combination of pressing the volume buttons and power button at the same time.