Those preview links expire after 24 hours IIRC. Link, I don't necessarily think you need to restructure. More info is better when it comes to these articles. I like the ones that don't assume too much knowledge on the part of the user. Paul On Tue, Jul 4, 2017 at 3:39 AM, Stuart Brady <sbrady1215@xxxxxxxxx> wrote: > Oh, I was about to edit this but I now get a 404 error on the link. > > On Tue, Jul 4, 2017 at 1:09 PM, Link Dupont <link@xxxxxxxxxxx> wrote: > >> On Mon, 2017-07-03 at 14:47 -0400, Paul W. Frields wrote: >> > On Tue, Jun 27, 2017 at 10:40:11PM -0700, Link Dupont wrote: >> > > Hi everyone, >> > > >> > > I've got a first draft up for part 1 of the Backing up series. >> > > Please >> > > read, follow and give me feedback. There are definitely areas that >> > > can >> > > be improved. >> > > >> > > Also, I don't want to publish until all three articles are done. I >> > > need >> > > to make sure that parts two and three (duply and deja-dup, >> > > respectively) will work seamlessly with the backup created in part >> > > one. >> > > This may mean significant edits to this part one. >> > > >> > > Please provide feedback! >> > > >> > > https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880 >> > >> > The coverage of this article is absolutely spot-on. It's easy to >> > follow and gives clear directions. >> > >> > I recommend you make a pass over it, though, and try to shorten and >> > simplify sentences. A good rule of thumb is to minimize the use of >> > the verb "to be," along with gerunds ("-ing" words). For example: >> > >> > FROM: "Backups are only as good as how often they are run. Backups >> > need to be scheduled and run regularly in order to keep adding new >> > data and pruning off old data." >> > >> > TO: "Backups only help if you run them often. Schedule and run them >> > regularly to keep adding new data and prune off old data." >> > >> > This might seem nitpicky, but writing becomes stronger when you make >> > sentences short, and use a declarative or commanding tone. Don't >> > labor over it too long though! ;-) Do what you can and I'll be glad >> > to >> > help tune it later. >> > >> > -- >> > Paul W. Frields http://paul.frields.or >> > g/ >> > gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 >> > http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ >> > The open source story continues to grow: http://opensource.com >> > _______________________________________________ >> > Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx >> > To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxx >> > g >> >> Perfect feedback. I'll give that a pass. Do you think there's too much >> time spent on setting up AWS? I was thinking about a slight >> restructuring of the article to focus more on duplicity, and leave most >> of the AWS stuff up to the user. Basically writing the article assuming >> that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY >> already and just telling them to plug them in. >> _______________________________________________ >> Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx >> >> > _______________________________________________ > Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx
