paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-02 13:03:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Spell "front end" as "frontend" consistently.

Browse Source 
I think it makes sense avoid diversity here.
This commit is contained in:
Thomas Güttler
2020-09-12 20:41:35 +02:00
committed by GitHub
parent 45cd979d46
commit 740a4a1eff
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tutorials/new-feature-tutorial.md
View File

@@ -482,10 +482,10 @@ the setting enabled).
Visit Zulip's [Django testing](../testing/testing-with-django.md)
documentation to learn more about the backend testing framework.
### Update the front end
### Update the frontend
After completing the process of adding a new feature on the back end,
you should make the required front end changes: in this case, a checkbox needs
you should make the required frontend changes: in this case, a checkbox needs
to be added to the admin page (and its value added to the data sent back
to server when a realm is updated) and the change event needs to be
handled on the client.
@@ -621,9 +621,9 @@ Here are few important cases you should consider when testing your changes:
buttons, so changes and saving in one subsection shouldn't affect
the others.
### Front end tests
### Frontend tests
A great next step is to write front end tests. There are two types of
A great next step is to write frontend tests. There are two types of
frontend tests: [node-based unit tests](../testing/testing-with-node.md) and
[Puppeteer end-to-end tests](../testing/testing-with-puppeteer.md).