Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos in notebooks.md and a plenty of relative links #6089

Merged
merged 10 commits into from
May 16, 2023
Prev Previous commit
Next Next commit
Fix invalid relative links in markdown files
  • Loading branch information
pavoljuhas committed May 6, 2023
commit b3f0b73bbf50c09b7949bd1d6de7a6e024233936
2 changes: 1 addition & 1 deletion dev_tools/cirq-infra/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
This doc describes cirq-infra, the GCP project supporting our open source project.
The following things are planned to be running on GCP:

- [X] Cirq bot / Automerge - see [../auto_merge](../auto_merge/README.md)
- [X] Cirq bot / PR monitor - see [../pr_monitor](../pr_monitor/README.md)
- [X] Triage party for triaging
- [ ] Performance tests and reports

Expand Down
2 changes: 1 addition & 1 deletion release.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Master will always use the next unreleased minor version with the suffix
of ".dev". When a release is performed, the ".dev" will be removed and tagged
in a release branch with a version tag (vX.X.X). Then, master will be updated
to the next minor version. This can always be found in the
[version file](cirq/_version.py).
[version file](./cirq-core/cirq/_version.py).

### Release Schedule
Releases are made on an as-needed basis determined by Cirq maintainers. All Cirq
Expand Down