@@ -221,7 +221,7 @@ Proper commit messages are important as they allow to speed up the review proces
### Editing previous commits
While implementing your topic that would be holding multiple commits, you might end up making changes which should be coupled with or which revert changes from previous commits. The same thing can happen when your merge request has been reviewed and you need to make changes that should be applied in existing commit.
While implementing your topic that would be holding multiple commits, you might end up making changes which should be coupled with or which revert changes from previous commits. The same can happen when your merge request has been reviewed and you need to make changes that should be applied in an existing commit.
It is possible to change previous commits in order to keep your topic clean and make the reviewing process easier, a couple options are listed below.
...
...
@@ -367,7 +367,7 @@ This process consists of rewriting the branch history, therefore re-syncing it w
* ### Add Data
The proper way to add data to iMSTK, is to:
- Contact a project manager to upload your data in the [Girder iMSTK collection](https://data.kitware.com/#collection/58ab34918d777f073240dc02).
- Contact a project manager to upload your data in the [Girder's iMSTK collection](https://data.kitware.com/#collection/58ab34918d777f073240dc02).
- Add the key file to `iMSTK-Source/Data` (Download the key file from girder as shown on the following picture).