[website] use the `infer command` form instead of `infer-command`

Summary: Seems better and more consistent with most uses.

Reviewed By: ezgicicek

Differential Revision: D21525864

fbshipit-source-id: 85dca8d6e

website/docs/01-infer-workflow.md

@@ -16,7 +16,7 @@ own project.
    for instance if you are analyzing single files with
    `infer run -- javac Hello.java`.
 4. After a successful Infer run, you can explore Infer's reports in more details
-   by running `infer-explore` from the same directory.
+   by running `infer explore` from the same directory.
 
 ## The two phases of an Infer run
 
@@ -178,13 +178,13 @@ The list of build systems supported by Infer is detailed in the
 ## Exploring Infer reports
 
 You can get more information about the reports generated by Infer by running
-`infer-explore` in the same directory. For instance
+`infer explore` in the same directory. For instance
 
 ```bash
 infer run -- gradle build
-infer-explore
+infer explore
 ```
 
 This tool allows you to see error traces leading to each bug reported by Infer,
 which can be helpful in tracking down the precise cause of each bug. See the
-output of `infer-explore --help` for more information.
+output of `infer explore --help` for more information.

website/docs/01-man-pages.md

@@ -6,10 +6,10 @@ title: Infer Manuals
 Here are the man pages for all the infer commands:
 
 - [infer](/man/infer.1.html)
-- [infer-analyze](/man/infer-analyze.1.html)
-- [infer-capture](/man/infer-capture.1.html)
-- [infer-compile](/man/infer-compile.1.html)
-- [infer-explore](/man/infer-explore.1.html)
-- [infer-report](/man/infer-report.1.html)
-- [infer-reportdiff](/man/infer-reportdiff.1.html)
-- [infer-run](/man/infer-run.1.html)
+- [infer analyze](/man/infer-analyze.1.html)
+- [infer capture](/man/infer-capture.1.html)
+- [infer compile](/man/infer-compile.1.html)
+- [infer explore](/man/infer-explore.1.html)
+- [infer report](/man/infer-report.1.html)
+- [infer reportdiff](/man/infer-reportdiff.1.html)
+- [infer run](/man/infer-run.1.html)