spelling fix
This commit is contained in:
@@ -47,7 +47,7 @@ gardens like Facebook/Instagram/Twitter/Medium that make it super easy
|
||||
to get content *in*, but very difficult to get it back *out*. [Twitter
|
||||
killed RSS in 2012](http://mashable.com/2012/09/05/twitter-api-rss), and
|
||||
have you ever tried to get a list of your most recent Instagram photos
|
||||
programatically? I wouldn't. Owning your own content and sharing it
|
||||
programmatically? I wouldn't. Owning your own content and sharing it
|
||||
liberally is what the web was made for, and JSON Feed has the potential
|
||||
to make it easy and fun to do. [It's how things should be. It's how they
|
||||
could be.](https://www.youtube.com/watch?v=TgqiSBxvdws)
|
||||
|
||||
@@ -56,7 +56,7 @@ works](https://github.com/tommeier/delayed_paperclip) from tommeier. I
|
||||
recommend using the
|
||||
[rescue-ensure-connected](https://github.com/socialcast/resque-ensure-connected)
|
||||
gem if you're going to run Resque in production to keep your
|
||||
long-running processes from losing their DB connnections.
|
||||
long-running processes from losing their DB connections.
|
||||
|
||||
## Server Configuration
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ result is a geometry string which crops the image, repages it, then
|
||||
scales the image and crops it a second time. Simple, but not certainly
|
||||
not intuitive, at least not to me.
|
||||
|
||||
From here, you can include this cropper using the `:processers`
|
||||
From here, you can include this cropper using the `:processors`
|
||||
directive in your `has_attached_file` declaration, and you should be
|
||||
good to go. This simple approach assumes that the crop dimensions will
|
||||
always be set, so tweak accordingly if that's not the case.
|
||||
|
||||
Reference in New Issue
Block a user