Browse files

Merge pull request #234 from soy714/prose-patch

Updated _posts/help/2012-06-20-internals.md
  • Loading branch information...
2 parents e52957f + 97da582 commit 2b72ddd6bfbcc99cd913ef4465ebe1b57c0ac42f Michael Aufreiter committed Aug 29, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 _posts/help/2012-06-20-internals.md
View
4 _posts/help/2012-06-20-internals.md
@@ -13,7 +13,7 @@ published: true
Prose is just a static webpage and doesn't require any server-side bits. Instead it interacts directly with the GitHub API for managing your repo's contents. This means there's nothing to setup, no database no fileserver etc. This is imporant because we want to make it easy for you to get involved in the development.
-Using just the GitHub API for powering our editor was not easy. GitHub just offers a low level API (around trees and blobs), which is challening in many cases, as it requires a lot of subsequent requests to do simple things, which slows down site performance. That's why creating a good architecture was crucial to manage the complexity. We ended up in abstracting the data layer into a separate module, Github.js.
+Using just the GitHub API for powering our editor was not easy. GitHub just offers a low level API (around trees and blobs), which is challenging in many cases, as it requires a lot of subsequent requests to do simple things, which slows down site performance. That's why creating a good architecture was crucial to manage the complexity. We ended up in abstracting the data layer into a separate module, Github.js.
## Github.js
@@ -70,4 +70,4 @@ The GitHub API comes with a number of limitations because of its low-level natur
- Deleting and renaming files
- This requires a full tree to be written involving a new commit that points to that tree. In fact this is not a big problem with small repositories, but once they get bigger it's not only a performance issue, you'll get errors. Be aware that you may not (yet) be able to rename or delete files when working with bigger repositories.
+ This requires a full tree to be written involving a new commit that points to that tree. In fact this is not a big problem with small repositories, but once they get bigger it's not only a performance issue, you'll get errors. Be aware that you may not (yet) be able to rename or delete files when working with bigger repositories.

0 comments on commit 2b72ddd

Please sign in to comment.