Location: Street, City, State/Prov, Postal Code & Country text is formatted incorrectly in reference to respective text fields

If you enable the location module for a content type like story or survey on your web site and then configure the CivicSpace theme as default, you will see some formatting issues for the location module's title text when entering location information for Location Name:, Street:, Additional:, City:, State/Province:, Postal Code: & Country:. Location Name is fine since it appears top-left of its respective text field, but all of the other titles appear on the right-hand side of the previous text field making it confusing to understand where to enter the street address, City, etc.. See the screenshot attachment theme_bug.jpg.

Initial Conditions
1. Use http://civicspacelabs.org to view this bug since I have already configured the problem here.
2. The civicspace theme must be set to "enabled" & "default" -- admin/themes
3. A content type must be configured to have locative information enabled. -- admin/node/configure/types/[story]
(Story is just one example; in this bug I'm using a flexinode that I have created for a project)
4. Check "Enable for locations" and allow or require "Location names:", "Street locations:", "City names:", "State/Province names:", "Postal codes:"
& "Country names:"
5. Save configuration.

Steps-to-Reproduce
1. Create content -- http://civicspacelabs.org/home/node/add
2. Click CivicSpace Service Provider Survey.
3. Scroll down to the bottom of the screen.
4. View the location text field section.

Results
5. Notice that while "Location Name:" is correctly positioned on top of its text field to the left, all of the other text field titles are formatted
incorrectly to the right-hand side of the previous text field (You're supposed to enter City in the field that has "State/Province:" printed to
the right of it) except "Country:" which is on top of its field but positioned incorrectly more to the right. See the screenshot attachment
theme_bug.jpg.

Notes.
1. This issue is a theme problem and has nothing to do with the web browser. I can see the same issue with Safari.