Skip to content

Commit

Permalink
Fix some typos
Browse files Browse the repository at this point in the history
  • Loading branch information
popod authored Mar 7, 2018
1 parent 130311e commit 9880d01
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/tutorials/release-using-channels.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@
# Release Using Channels / Auto-Updates With Channels

## Description
Channels are useful to distribute "beta" or "alpha" releases of your application to a choosen set of users. This allow to test an application before release it as "stable".
Channels are useful to distribute "beta" or "alpha" releases of your application to a chosen set of users. This allows to test an application before release it as "stable".

Users which receive "beta" version will get "stable" versions too. Otherwise users who doesn't wanna "beta" will only get "stable" releases.
Users which receive "beta" version will get "stable" versions too. Otherwise, users who don't want "beta" will only get "stable" releases.

They are tree channels level ordered by stability :
They are tree channels level ordered by stability:
1. "stable", your application is stable and this is the default one (example: "1.3.2")
2. "beta" which mean your application works, but should have some bugs (example: "1.3.2-beta")
3. "alpha" which mean your application is not stable and in active development (example: "1.3.2-alpha")
2. "beta" which means your application works, but should have some bugs (example: "1.3.2-beta")
3. "alpha" which means your application is not stable and in active development (example: "1.3.2-alpha")


## Configuration
Expand All @@ -29,7 +29,7 @@ If you want to use channels, you should add this to your package.json:
}
```

> Note: `allowDowngrade` is automatically set to `true` when `generateUpdatesFilesForAllChannels = true`, so you doesn't need to set it.
> Note: `allowDowngrade` is automatically set to `true` when `generateUpdatesFilesForAllChannels = true`, so you don't need to set it.
All you have to do to release using channels is to define the channel in the version tag of the `package.json`. Add "-beta" or "-alpha" (nothing for stable) to automatically build for the related channel.

Expand All @@ -50,6 +50,6 @@ Imagine your application version is 1.0.1 (stable).

If you want to release a beta for the 1.1.0 version, you only need to update the package.json "version" with "1.1.0-beta".

And when your application is stable enouth and you want to release it to all users, only remove the "-beta" tag from the package.json "version" tag.
And when your application is stable enough and you want to release it to all users, only remove the "-beta" tag from the package.json "version" tag.


0 comments on commit 9880d01

Please sign in to comment.