By "the user visible name" do you mean the title in the title bar of the application?

(In reply to comment #1)
> By "the user visible name" do you mean the title in the title bar of the
> application?

No, this refers to the bold label in the dialog reachable by clicking on "About Documents" in the application menu.

Created attachment 211299 [details] [review]
Title of application "Gnome-Documents" instead of "Documents"

(In reply to comment #3)
> Created an attachment (id=211299) [details] [review]
> Title of application "Gnome-Documents" instead of "Documents"

Hey Anna! Patches should be attached to bug reports in a diff format; you can use `git diff` to get a diff between the current state of the code and the last commit in the branch, or `git format-patch` to turn a git commit itself into a patch.
You can also use git-bz [1], which is a nice tool designed to make it easy to interact with bugzilla reports from a git repo.

As for the code itself, I think you got the intent of this bug report backwards; right now we show 'Documents' as an application name everywhere except for the aforementioned string in the About dialog. That string should be modified to read "Documents" too, instead of "GNOME Documents".

[1] http://fishsoup.net/software/git-bz/

Created attachment 211322 [details] [review]
Change to About Dialog

Review of attachment 211322 [details] [review]:

Getting better! I have a comment on this patch below.

::: src/mainWindow.js
@@ -251,3 @@
                                 'William Jon McCann <william.jon.mccann@gmail.com>' ];
         aboutDialog.translator_credits = _("translator-credits");
-        aboutDialog.program_name = _("Gnome-Documents");

You seem to change the string from "Gnome-Documents" to "Documents" in the patch, but the current string in git master is "GNOME Documents". Are you sure the patch you published is not actually applied on top on another modification you did previously?

Created attachment 211340 [details] [review]
From "GNOME Documents" to "Documents"

Review of attachment 211340 [details] [review]:

Yes, thanks! Looks good!

Since this touches an user visible string, we should hold on committing this to git master until after I branch the application for the new 3.6 development cycle.

This is now pushed to master.