aljaz/pear-docs
1
0
Fork 0
mirror of https://github.com/aljazceru/pear-docs.git synced 2025-12-17 06:24:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix spelling mistakes (#150)

Browse Source
This commit is contained in:
Sean Zellmer
2024-10-22 08:07:06 -05:00
committed by GitHub
parent b4ad921fde
commit c0956c273d
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide/releasing-a-pear-app.md
View File

@@ -74,7 +74,7 @@ A development application link can be shared among trusted peers. At that point,
While using different channel names is sensible, using `pear stage dev` and `pear stage production` on the same machine has practical implications.
A dump-stage-release strategy seperates the concerns between development and production, by using a different machine for each.
A dump-stage-release strategy separates the concerns between development and production, by using a different machine for each.
On the machine that holds the production link, run:

2
guide/sharing-a-pear-app.md
View File

@@ -154,7 +154,7 @@ When Pear loads an application from a peer the staged files are sparsely replica
The command signature for `pear seed` is `pear seed <channel|link> [dir]`.
If the application was staged on the machine, it will seed the appliction from the machine.
If the application was staged on the machine, it will seed the application from the machine.
Otherwise, passing an application link to `pear seed` will reseed the application from that link.