I think having documentation in parenthesis makes it sound more like
something you don't need to read. I don't want to overwhelm the reader.
(but maybe my expectations about how the reader sees it are wrong...)


On Tue, May 13, 2014 at 12:28 AM, Andrew Phillips
<notifications@github.com>wrote:

> In guides/google.md:
>
> > +2. [Authentification](#auth)
> > +2. [Running examples](#examples)
> > +
> > +
> > +## <a id="intro"></a>Introduction
> > +This guide helps you to get started with [Google Cloud Platform](https://cloud.google.com/) development using jclouds.
> > +
> > +Currently, [Google Compute Engine](https://developers.google.com/compute/) is covered. This is a service that allows you to run vitual machines on Google's infrastructure.
> > +
> > +This guide assumes you have a Google Cloud project. If not yet, you can sign up on the [Developer Console](https://console.developers.google.com/
> ). For GCE, you need to set up billing.
> > +
> > +## <a id="auth"></a>Authentification
> > +Google Cloud Platform uses OAuth which gives a variety of choices how to authentificate:
> > +  * One can ask a user for consent to perform operations in his/her name.
> > +  * One can create a service account and use its private key to authentificate.
> > +  * Unless configured otherwise, programs running on a GCE instance can perform operations as the project's default service account ([documentation](https://developers.google.com/compute/docs/authentication)).
>
> Rather than having "(documentation)" in a link, make "default service
> account" itself the link?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds-site/pull/98/files#r12557507>
> .
>