Skip to content

Commit 83aaed8

Browse files
authored
#1142 fix more typos in the new xcodebuild formatter page
2 parents e2777e6 + a0f6bec commit 83aaed8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/best-practices/xcodebuild-formatters.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,12 @@ scan(
2626
xcodebuild_formatter: "xcpretty"
2727
)
2828

29-
# Specificy a local install of xcbeautify
29+
# Specify a local install of xcbeautify
3030
scan(
3131
xcodebuild_formatter: "/custom/path/to/xcbeautify"
3232
)
3333

34-
# Specifify your own custom formatter
34+
# Specify your own custom formatter
3535
scan(
3636
xcodebuild_formatter: "/custom/path/to/my_formatter"
3737
)
@@ -72,5 +72,5 @@ Historically, _fastlane_ was tightly integrated with [xcpretty](https://github.c
7272
- Generate an HTML report
7373
- Generate a JSON compilation database
7474

75-
**Before 2.201.0**, [_scan_](/actions/scan/) used `xcpretty` to generate these files and determine success/failure with `xcpretty` output
76-
<br/>**As of 2.201.0**, [_scan_](/actions/scan/) will only generate these if `xcodebuild_formatter` is using `xcpretty` but now use `trainer` to parse test results to determine success/failure
75+
**Before 2.201.0**, [_scan_](/actions/scan/) used `xcpretty` to generate these files and determine success/failure with `xcpretty` output.<br/>
76+
**As of 2.201.0**, [_scan_](/actions/scan/) will only generate these if `xcodebuild_formatter` is using `xcpretty` but now use `trainer` to parse test results to determine success/failure.

0 commit comments

Comments
 (0)