Update URLs for new atom org location
This commit is contained in:
parent
b23da34ce9
commit
ac77c9df54
2 changed files with 4 additions and 4 deletions
2
brightray/.gitmodules
vendored
2
brightray/.gitmodules
vendored
|
@ -1,6 +1,6 @@
|
|||
[submodule "vendor/libchromiumcontent"]
|
||||
path = vendor/libchromiumcontent
|
||||
url = https://github.com/brightray/libchromiumcontent
|
||||
url = https://github.com/atom/libchromiumcontent
|
||||
[submodule "vendor/gyp"]
|
||||
path = vendor/gyp
|
||||
url = https://github.com/svn2github/gyp
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
# Brightray
|
||||
|
||||
Brightray is a static library that makes
|
||||
[libchromiumcontent](https://github.com/brightray/libchromiumcontent) easier to
|
||||
[libchromiumcontent](https://github.com/atom/libchromiumcontent) easier to
|
||||
use in applications.
|
||||
|
||||
## Using it in your app
|
||||
|
||||
See [brightray_example](https://github.com/brightray/brightray_example) for a
|
||||
See [brightray_example](https://github.com/atom/brightray_example) for a
|
||||
sample application written using Brightray.
|
||||
|
||||
## Development
|
||||
|
@ -34,7 +34,7 @@ You must previously have built and uploaded libchromiumcontent using its
|
|||
|
||||
Building Brightray on its own isn’t all that interesting, since it’s just a
|
||||
static library. Building it into an application (like
|
||||
[brightray_example](https://github.com/brightray/brightray_example)) is the only
|
||||
[brightray_example](https://github.com/atom/brightray_example)) is the only
|
||||
way to test it.
|
||||
|
||||
## License
|
||||
|
|
Loading…
Reference in a new issue