Update links to the Lightbend GitHub organization

Author: jonas

README.md

@@ -1,6 +1,6 @@
 # GenJavaDoc
 
-[![Build Status](https://travis-ci.org/typesafehub/genjavadoc.svg?branch=master)](https://travis-ci.org/typesafehub/genjavadoc)
+[![Build Status](https://travis-ci.org/lightbend/genjavadoc.svg?branch=master)](https://travis-ci.org/lightbend/genjavadoc)
 
 This project’s goal is the creation of real JavaDoc for Scala projects. While ScalaDoc—the native API documentation format of Scala—has several benefits over JavaDoc, Java programmers are very much used to having access to API documentation in a syntax matching their programming language of choice. Another motivating factor may be that javadoc-JARs are supported within IDE, e.g. showing tooltip help texts.
 

RELEASING.md

@@ -1,9 +1,9 @@
 ## Creating a regular release
 
-1. Create a [new release](https://github.com/typesafehub/genjavadoc/releases/new) with:
+1. Create a [new release](https://github.com/lightbend/genjavadoc/releases/new) with:
   * the next tag version (e.g. `v0.11`)
   * title and release description including notable changes
-  * link to the [milestone](https://github.com/typesafehub/genjavadoc/milestones) showing an overview of closed issues for this release
+  * link to the [milestone](https://github.com/lightbend/genjavadoc/milestones) showing an overview of closed issues for this release
 2. Checkout the newly created tag and publish the release by running `sbt publishSigned`. You will have to have Sonatype OSS repository rights to publish under `com.typesafe` organisation.
 3. Login to [Sonatype](https://oss.sonatype.org/) to close and release the repository.
 
@@ -16,4 +16,4 @@ It is often the case when this compiler plugin needs to be released for a newly
   * tag, if the master has unlrealeased features or bug fixes. In this case you will need to cherry pick the commit that adds support for the new Scala version.
 2. Create a file `version.sbt` containing `version in ThisBuild := "0.11"` which sets the version to be back-released. This will override the automatic version derivation from the git history.
 3. Publish the release by running `sbt publishSigned`. You will have to have Sonatype OSS repository rights to publish under `com.typesafe` organisation.
-4. Login to [Sonatype](https://oss.sonatype.org/) to close and release the repository.
+4. Login to [Sonatype](https://oss.sonatype.org/) to close and release the repository.

build.sbt

@@ -76,7 +76,7 @@ lazy val defaults = Seq(
   },
   pomExtra :=
     (<inceptionYear>2012</inceptionYear>
-     <url>http://github.com/typesafehub/genjavadoc</url>
+     <url>http://github.com/lightbend/genjavadoc</url>
      <licenses>
        <license>
          <name>Apache 2</name>
@@ -85,8 +85,8 @@ lazy val defaults = Seq(
        </license>
      </licenses>
      <scm>
-       <url>git://github.com/typesafehub/genjavadoc.git</url>
-       <connection>scm:git:git@github.com:typesafehub/genjavadoc.git</connection>
+       <url>git://github.com/lightbend/genjavadoc.git</url>
+       <connection>scm:git:git@github.com:lightbend/genjavadoc.git</connection>
      </scm>) ++ makeDevelopersXml(Map(
       "rkuhn" -> "Roland Kuhn")))