update

CONTRIBUTING.md

@@ -23,7 +23,7 @@ If you have a contribution for our [documentation](https://developer.chrome.com/
 1. If your issue has been discussed and it seems no one else is working on it, drop a note saying you plan to work take it. Feel free to ask questions. If your planned patch has no open issue already, it'd be best to first open an issue where you describe your idea and wait for us to give feedback.
 1. Fork the repo (unless you are a core contributor, then the preference is to use the main repo), develop and test your code changes.
 1. Ensure that your code adheres to the existing style in the sample to which you are contributing. In addition, run `yarn lint --fix`.
-1. We have quite a few files checked in that are derived from source files. With any change, it's good to ensure everything is up-to-date by running this command: `yarn build-report && yarn lint --fix && yarn type-check && yarn update:sample-json && yarn i18n:collect-strings`.
+1. We have quite a few files checked in that are derived from source files. With any change, it's good to ensure everything is up-to-date by running this command: `yarn build-report && yarn update:sample-json && yarn lint --fix`.
 1. You may also find some tests need to be updated. Run `yarn unit` and `yarn smoke` to ensure nothing broke.
 1. Submit a pull request.
 1. Sign a Contributor License Agreement ([see details below](#sign-the-contributor-license-agreement)).