See my comments at issue 716658. Not sure if it makes sense to keep those bugs as separate, since the requested changes affect the exact same code for both ChromeOS and non-ChromeOS.

Updated specs: 

In the legal copy "Chrome OS is made possible by additional open source software", the "open source software" was not linkified – and it should be (as it is today)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7cf21a287bc149f34de83c2bb57b61e6d206fa6b

commit 7cf21a287bc149f34de83c2bb57b61e6d206fa6b
Author: dpapad <dpapad@chromium.org>
Date: Tue May 16 19:31:55 2017

MD Settings: About page, move copyright text in it's own card.

BUG=716658,716656
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2888493002
Cr-Commit-Position: refs/heads/master@{#472184}

[modify] https://crrev.com/7cf21a287bc149f34de83c2bb57b61e6d206fa6b/chrome/browser/resources/settings/about_page/about_page.html

bettes: Why is the logo spelled like "chromeOS"? Normally the product is called "Chrome OS" or "Chromium OS", without a space and with a capital C. Is this an intentional change or something we already do?

@bettes: See michaelpg's question at comment #8. I would like to double check that we have the right logo's before starting to implement this.

Revision to comment #1, #1:
SVG assets included below. The logo is separated from the wordmark as separate svgs.

https://drive.google.com/open?id=0BxMIIGI80eU-OGtOVEtvZ3RpRFk

Export settings set based off this guidance:

https://docs.google.com/presentation/d/18Z8nAbaiO1oPuG0yvWw60c52tKcNhMd3gLGOaJgOSWY/edit#slide=id.g1b051ee056_0_0

Deleted: Screen Shot 2017-05-22 at 4.59.49 PM.png 66.2 KB

	Screen Shot 2017-05-22 at 4.59.49 PM.png 66.2 KB View Download

#10: The question in #8 is why the wordmark, "chromeOS", is not "Chrome OS" (the name of the product).

I noticed the "chromeOS" text in a similar font go up in MTV-40-2 and it was kind of unsettling. Did we actually change our name?

Chrome has many UI strings containing "Chrome OS", one containing "ChromeOS" (which I will fix), and zero that I can find containing "chromeOS".

So yes, if the name of the product has been changed to something other than "Chrome OS", please announce that to the team and come up with a plan to update all of the places where we currently use "Chrome OS" publicly (including the links at the bottom of https://www.google.com/chromebook/ and https://www.google.com/chromebook/about/).

+shussain

In a thread from late-2015 we discussed switching to the "chromebook" logo (even for Chrome{bit/box/base} devices). However since then I've seen a "chromeOS" logo in more places, including the wall of our office :-) Is that official, or should we stick with "chromebook" if we need a logo to use?

I think that that's a separate issue. I'm not aware of any disagreement about what we call the physical devices -- we've always used "Chromebook", "Chromebox", etc.

Michael's question was about what we call the software that we put on devices. We (Google) don't refer to it often publically, but in the places where we do, we currently use "Chrome OS" (see e.g. chrome://help).

Internally, everything is a huge mess. People on the team probably use "ChromeOS" nearly as often (if not more than) "Chrome OS", which I find a bit embarrassing. Changing one spot in the UI to read "chromeOS" will just confuse matters further.

This is probably veering into a place where we should have an offline discussion.

1. I've been instructed to refer to the Chromebook as "ChromeOS" in the about page from the CrOS UX team. Debating this issue should be done in email, not bugs. 

2. The wordmark given to me is "ChromeOS", not "Chrome OS" so that's what you see here

3. There's no plan to update the product names from Chrome OS to ChromeOS, as far as I know. I think that should be filed separately. 

The spacing between cards is not to spec. Expected is 16px. See my comment in #1: 

>> *** Spec below is measured at 2x so divide numbers in half. Sorry :/ ***

Marking bugs (mostly lower priority ones) that I am unlikely to get to soon as Available.

Here's an attempt CL I made a while ago in case someone wants to pick it up:
https://chromium-review.googlesource.com/c/chromium/src/+/882013