Capitalize waiting state messages that form the main content of their dialogs and make them more pr…

remoting/webapp/_locales/en/messages.json

 {
   "ACCESS_CODE": {
     "message": "Access code",
     "description": "Label for the access code entry box. This is where the client user enters the code that permits access to the host."
   },
   "ACCESS_CODE_TIMER": {
     "message": "This access code will expire in $timeout$",
     "description": "Text displayed when the access code is due to time out within 30 seconds.",
     "placeholders": {
       "timeout": {
@@ skipping 156 matching lines @@
     "description": "Error displayed by the client if the server does not respond to a network request."
   },
   "ERROR_SERVICE_UNAVAILABLE": {
     "message": "The service is temporarily unavailable. Please try again later.",
     "description": "Error displayed when the service returns a 503 error. Such errors are usually temporary, and resolve themselves in about 30 seconds."
   },
   "ERROR_UNEXPECTED": {
     "message": "An unexpected error occurred. Please report this problem to the developers.",
     "description": "Error displayed in situations where things go wrong in ways not anticipated by the developers. There is typically no user-workaround to suggest, other than reporting the error so that we can investigate further."
   },
+  "FOOTER_CONNECTING": {
+    "message": "Connecting\u2026",
+    "description": "Text displayed while a client is connecting to a host, but before the connection is established."

[simonmorris, 2012/05/01 18:30:30]

Maybe the description should start "Footer text displayed at the client...", for
consistency with the next item?

[Jamie, 2012/05/01 19:19:00]

It's not really a footer in the same sense that the host is. TBH, neither of
them are footers in the way that they were when these descriptions were first
written, but the host-side appears underneath some substantial UI, whereas the
client exists on its own.

+  },
   "FOOTER_WAITING": {
     "message": "waiting for connection\u2026",

[simonmorris, 2012/05/01 18:30:30]

Should this be capitalized, for consistency with the previous item?

[Jamie, 2012/05/01 19:19:00]

No, for the above reason. The client-side text is pretty much the only thing in
the dialog, so it's rendered black and in sentence-case. The host-side is
incidental, so it's grey and doesn't have a capital letter.

     "description": "Footer text displayed at the host after an access code has been generated, but before a client connects."
   },
   "FULL_SCREEN": {
     "message": "Full screen",
     "description": "Menu option for toggle full-screen mode. Equivalent to using the Wrench menu to do the same thing."
   },
   "GET_STARTED": {
     "message": "Get started",
     "description": "Button displayed underneath explanatory text for app features. Clicking causes the text, infographic and the button itself to be replaced by the actual UI for that feature."
   },
@@ skipping 55 matching lines @@
   },
   "HOST_SETUP_STARTED": {
     "message": "Remote connections for this computer have been enabled.",
     "description": "Message shown after access to local computer has been enabled successfully."
   },
   "HOST_SETUP_STARTED_DISABLE_SLEEP": {
     "message": "Please check your computer's power management settings and ensure that it is not configured to sleep when idle.",
     "description": "Instructions to the user to ask them to disable power management for the computer in order to be able to connect to it."
   },
   "HOST_SETUP_STARTING": {
-    "message": "enabling remote connections for this computer\u2026",
+    "message": "Enabling remote connections for this computer\u2026",
     "description": "Message shown when local machine is being registered in the directory and when starting the host."
   },
   "HOST_SETUP_STOP_FAILED": {
     "message": "Failed to disable remote access to this computer. Please try again later.",
     "description": "Message shown after we've failed to stop the host."
   },
   "HOST_SETUP_STOPPED": {
     "message": "Remote connections for this computer have been disabled.",
     "description": "Message shown after host has been stopped."
   },
   "HOST_SETUP_STOPPING": {
-    "message": "disabling remote connections for this computer\u2026",
+    "message": "Disabling remote connections for this computer\u2026",
     "description": "Message shown when host is being stopped on the local machine."
   },
   "HOST_SETUP_UPDATED_PIN": {
-    "message": "PIN has been updated.",
+    "message": "Your PIN has been updated.",
     "description": "Message shown after changing PIN for the local computer."
   },
   "HOST_SETUP_UPDATING_PIN": {
-    "message": "PIN for this computer is being updated\u2026",
+    "message": "The PIN for this computer is being updated\u2026",
     "description": "Message shown while changing PIN for the local computer."
   },
   "HOST_SETUP_UPDATE_PIN_FAILED": {
     "message": "Failed to update the PIN. Please try again later.",
     "description": "Message shown we fail to update PIN for the local computer."
   },
   "HOME_SHARE_BUTTON": {
     "message": "Share",
     "description": "Clicking this button starts the desktop sharing process."
   },
@@ skipping 167 matching lines @@
   },
   "WARNING_NAT_DISABLED": {
     "message": "NOTE: Policy settings permit connections only between computers within your network.",
     "description": "Message displayed at the bottom of the host screen if local policy dictates that NAT traversal is disabled, meaning that connections outside the local network will not work."
   },
   "WHY_IS_THIS_SAFE": {
     "message": "Why is this safe?",
     "description": "Help link displayed when the user enables the host on this computer. Clicking this link opens a page that explains why this operation is safe."
   }
 }