Don't say "K&R style" in coding conventions

Summary: We technically don't use K&R. These documents and the rest of the codebase are full of examples of the correct style, which should be unambiguous to a reasonable reader.

Test Plan: reading

Reviewers: staticshock, btrahan

Reviewed By: btrahan

Subscribers: epriestley

Differential Revision: https://secure.phabricator.com/D11255

src/docs/contributor/javascript_coding_standards.diviner

@@ -18,7 +18,6 @@ guidelines, you can probably get away with skimming this document.
 
   - Use two spaces for indentation. Don't use literal tab characters.
   - Use Unix linebreaks ("\n"), not MSDOS ("\r\n") or OS9 ("\r").
-  - Use K&R style braces and spacing.
   - Put a space after control keywords like ##if## and ##for##.
   - Put a space after commas in argument lists.
   - Put space around operators like ##=##, ##<##, etc.

src/docs/contributor/php_coding_standards.diviner

@@ -19,7 +19,6 @@ guidelines, you probably don't need to read this super thoroughly.
 
   - Use two spaces for indentation. Don't use tab literal characters.
   - Use Unix linebreaks ("\n"), not MSDOS ("\r\n") or OS9 ("\r").
-  - Use K&R style braces and spacing.
   - Put a space after control keywords like ##if## and ##for##.
   - Put a space after commas in argument lists.
   - Put a space around operators like ##=##, ##<##, etc.