Skip to main content
replaced http://serverfault.com/ with https://serverfault.com/
Source Link

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following editedit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. The edit comment of Grammar & formatting. suggests that this was a choice of the user, not a word processor.

Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. The edit comment of Grammar & formatting. suggests that this was a choice of the user, not a word processor.

Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. The edit comment of Grammar & formatting. suggests that this was a choice of the user, not a word processor.

Should we be performing these types of edits?

Tweeted twitter.com/#!/ServerFault/status/467160387386089472
added a note to clarify that word processor autocorrect is not involved, as a defensive measure against my counter-pendatry being countered by counter-counter-pedantry
Source Link
Andrew B
  • 33.5k
  • 15
  • 31

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. The edit comment of Grammar & formatting. suggests that this was a choice of the user, not a word processor.

Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. The edit comment of Grammar & formatting. suggests that this was a choice of the user, not a word processor.

Should we be performing these types of edits?

added 15 characters in body
Source Link
Andrew B
  • 33.5k
  • 15
  • 31

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped in forinto the post, obliterating their less efficientinferior ASCII counterparts. Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped in for their less efficient ASCII counterparts. Should we be performing these types of edits?

This isn't specific to SF, but it came up recently and it's worth a brief touch point. Recently in the review queue, I stumbled upon the following edit:

Before:

How do you troubleshoot Apache redirects in production? I know there's a a logging feature somewhere that lets you log all the redirects that happen...

After:

How do you troubleshoot Apache redirects on a production server? I know there’s a a logging feature somewhere that lets you log all the redirects that happen…

Aside from changing "in production" to "on a production server", the nuance is easily missed: the ’ and … Unicode characters were swapped into the post, obliterating their inferior ASCII counterparts. Should we be performing these types of edits?

Source Link
Andrew B
  • 33.5k
  • 15
  • 31
Loading