Skip to content

Fix outdated terminology #1639

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

Merged
merged 1 commit into from
Oct 19, 2020
Merged

Fix outdated terminology #1639

merged 1 commit into from
Oct 19, 2020

Conversation

oliversalzburg
Copy link
Contributor

The new branch names have not made it into all the documentation yet. This change fixes that.

If I need to create a dedicated issue prior to this, please let me know.

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • is from a uniquely-named feature branch and has been rebased on top of the latest master. (If I was asked to make more changes, I have made sure to rebase onto master then too)
  • is descriptively named and links to an issue number, i.e. Fixes #123

@catarak
Copy link
Member

catarak commented Oct 19, 2020

Thank you for fixing this! In the future, could you open an issue first before making a pull request? It helps with documentation of bugs/features/etc.

@catarak catarak merged commit 9db9db0 into processing:develop Oct 19, 2020
@oliversalzburg
Copy link
Contributor Author

Sure, I will do that. I assumed issues are only needed if a solution can't be provided right away. I'll keep this in mind. Sorry for the trouble.

@oliversalzburg oliversalzburg deleted the fix/readme branch October 19, 2020 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants