└── README.md


/README.md:
--------------------------------------------------------------------------------
 1 | ## AirPair Social Authoring
 2 | 
 3 | ### Thank you
 4 | 
 5 | Thanks for contributing content to [AirPair's community posts section](https://www.airpair.com/posts). This post authored by Greg Osuri can be edited at:
 6 | 
 7 | https://www.airpair.com/posts/edit/54f3d0b292e9370c00ae049f
 8 | 
 9 | ## Licensing of Content
10 | 
11 | Content submitted to AirPair with no monetary exchange belongs to the author. Contributors are
12 | granted rights to copy this content for the purpose of contributing, however under no circumstances
13 | do contributions grant co-ownership rights with the original author. This content may not be
14 | published anywhere other than airpair.com without the author's permission.
15 | 
16 | If any finacial exchange has occured between the author and AirPair, AirPair assumes ownership
17 | of this content and it may not be published, including by the author anywhere other than
18 | airpair.com without permission.
19 | 
20 | ## Author Instructions
21 | 
22 | #### Editing
23 | 
24 | All edits are tracked via this GitHub repo. You can use the AirPair editor to
25 | save changes back to this repo, or edit the markdown file with any tool of your choice.
26 | 
27 | #### Accepting contributions
28 | 
29 | All contributions come in the form of Pull Requests. Use GitHub to view and
30 | merge or reject Pull Requests.
31 | 
32 | #### Updating your post on AirPair
33 | 
34 | AirPair does not automatically sync with this repo. Propagating HEAD is a
35 | manual process which you can do, by clicking "Publish" during the community review phase.
36 | Once your post is fully published, updating AirPair from this repo will
37 | require an AirPair user with editor permissions.
38 | 
39 | ## Contributor Instructions
40 | 
41 | #### Editing
42 | 
43 | Before you start editing, if it's been more than a few hours since you forked this post,
44 | we highly recomment updating your fork so not to suggest edits on an old version of the post.
45 | 
46 | Edit your fork with the tool of your choice and then use GitHub to create a pull request from you
47 | fork with the original repo as your base.
48 | 


--------------------------------------------------------------------------------