match.md in fastlane-2.61.0

- old
+ new

@@ -80,11 +80,11 @@
 
 This will create a `Matchfile` in your current directory (or in your `./fastlane/` folder).
 
 Example content (for more advanced setups check out the [fastlane section](#fastlane)):
 
-```ruby
+```ruby-skip-tests
 git_url "https://github.com/fastlane/fastlane/tree/master/certificates"
 
 app_identifier "tools.fastlane.app"
 username "user@fastlane.tools"
 ```
@@ -196,27 +196,27 @@
 
 #### fastlane
 
 Add _match_ to your `Fastfile` to automatically fetch the latest code signing certificates with [fastlane](https://fastlane.tools).
 
-```ruby
+```
 match(type: "appstore")
 
-match(git_url: "https://github.com/fastlane/fastlane/tree/master/certificates",
+match(git_url: "https://github.com/fastlane/certificates",
       type: "development")
 
-match(git_url: "https://github.com/fastlane/fastlane/tree/master/certificates",
+match(git_url: "https://github.com/fastlane/certificates",
       type: "adhoc",
       app_identifier: "tools.fastlane.app")
 
-match(git_url: "https://github.com/fastlane/fastlane/tree/master/certificates",
+match(git_url: "https://github.com/fastlane/certificates",
       type: "enterprise",
       app_identifier: "tools.fastlane.app")
 
 # _match_ should be called before building the app with _gym_
 gym
-...
+# ...
 ```
 
 ##### Registering new devices
 
 By using _match_, you'll save a lot of time every time you add new device to your Ad Hoc or Development profiles. Use _match_ in combination with the [`register_devices`](https://docs.fastlane.tools/actions#register_devices) action.
@@ -230,10 +230,10 @@
 
 By using the `force_for_new_devices` parameter, _match_ will check if the device count has changed since the last time you ran _match_, and automatically re-generate the provisioning profile if necessary. You can also use `force: true` to re-generate the provisioning profile on each run.
 
 _**Important:** The `force_for_new_devices` parameter is ignored for App Store provisioning profiles since they don't contain any device information._
 
-If you're not using `fastlane`, you can also use the `force_for_new_devices` option from the command line:
+If you're not using _fastlane_, you can also use the `force_for_new_devices` option from the command line:
 
 ```no-highlight
 fastlane match adhoc --force_for_new_devices
 ```
 