Correct spelling of "phabrictor" in Lipsum and elsewhere

Summary: Ref T12319. The product name is misspelled in some methods, and a few places in the documentation.

Test Plan: `grep`

Reviewers: chad

Reviewed By: chad

Maniphest Tasks: T12319

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

src/docs/contributor/phabricator_code_layout.diviner

@@ -55,7 +55,7 @@ this document. See @{article:Adding New CSS and JS}.)
   phabricator/webroot/rsrc/css/application/derp/
 
 These directories under `phabricator/src/applications/derp/` represent
-the basic set of class types from which most Phabrictor applications are
+the basic set of class types from which most Phabricator applications are
 assembled. Each would contain a class file. For `Derp`, these classes could be
 something like:
 

src/docs/user/configuration/advanced_configuration.diviner

@@ -79,7 +79,7 @@ a config like this:
 To select a configuration file, write the name of the file (relative to
 `phabricator/conf/`) to `phabricator/conf/local/ENVIRONMENT`. For example, to
 select `phabricator/conf/custom/exampleconfig.conf.php`, you would write
-"custom/exampleconfig" to `phabrictor/conf/local/ENVIRONMENT`:
+"custom/exampleconfig" to `phabricator/conf/local/ENVIRONMENT`:
 
   phabricator/ $ echo custom/exampleconfig > conf/local/ENVIRONMENT
   phabricator/ $ cat conf/local/ENVIRONMENT

src/docs/user/userguide/audit.diviner

@@ -59,7 +59,7 @@ a typical audit workflow:
   - Alice publishes a commit containing some Javascript.
   - This triggers an audit request to Bailey, the Javascript technical
     lead on the project (see below for a description of trigger mechanisms).
-  - Later, Bailey logs into Phabrictor and sees the audit request. She ignores
+  - Later, Bailey logs into Phabricator and sees the audit request. She ignores
     it for the moment, since it isn't blocking anything. At the end of the
     week she looks through her open requests to see what the team has been
     up to.

src/docs/user/userguide/projects.diviner

@@ -37,7 +37,7 @@ only members of the "Backend" project, nor does it allow them to see it if they
 otherwise could not. Likewise, removing projects does not affect visibility.
 
 If you're familiar with other software that works differently, this may be
-unexpected, but the rule in Phabrictor is simple: **adding and removing
+unexpected, but the rule in Phabricator is simple: **adding and removing
 projects never affects policies.**
 
 Note that you //can// write policy rules which restrict capabilities to members