docs/upgrades/yolo-130.md in bullet_train-1.4.3 vs docs/upgrades/yolo-130.md in bullet_train-1.4.4
- old
+ new
@@ -134,11 +134,11 @@
```
(We have to do this since we didn't start explicitly tracking versions until `1.4.0` and
want to make sure that our gem versions match what the starter repo expects.)
-Then run `bundle update`
+Then run `bundle install`
Then go ahead and commit the changes.
```
git diff
@@ -245,11 +245,11 @@
```
(We have to do this since we didn't start explicitly tracking versions until `1.4.0` and
want to make sure that our gem versions match what the starter repo expects.)
-Then run `bundle update`
+Then run `bundle install`
Then go ahead and commit the changes.
```
git diff
@@ -270,9 +270,9 @@
```
git checkout main
git merge updating-bullet-train-v1.3.1
git push origin main
-git branch -d updating-bullet-train-v1.3.1`
+git branch -d updating-bullet-train-v1.3.1
```
-Alternatively, if you're using GitHub, you can push the `updating-bullet-train-v1.3.1` branch up and create a PR from it and let your CI integration do it's thing and then merge in the PR and delete the branch there. (That's what we typically do.)
+Alternatively, if you're using GitHub, you can push the `updating-bullet-train-v1.3.1` branch up and create a PR from it and let your CI integration do its thing and then merge in the PR and delete the branch there. (That's what we typically do.)