From a389cd9670cb89a490cf66da6b80b6c9ea5d0843 Mon Sep 17 00:00:00 2001 From: David Lechner Date: Tue, 20 Apr 2021 12:56:43 -0500 Subject: [PATCH] sets/boost/creative-toolbox/auto-builder: Remove code format from link. The two formatting styles don't play well together when rendered. --- sets/boost/creative-toolbox/auto-builder/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sets/boost/creative-toolbox/auto-builder/README.md b/sets/boost/creative-toolbox/auto-builder/README.md index 95fe9ff..fb1b850 100644 --- a/sets/boost/creative-toolbox/auto-builder/README.md +++ b/sets/boost/creative-toolbox/auto-builder/README.md @@ -41,7 +41,7 @@ The provided program is very basic, demonstrating only the core principles. Here's a few ideas and challenges for further exploration: - Change the order of the bricks in the `for`-loop to build something else. - Instead of pushing the element down for two seconds, you could stop sooner. - Try experimenting with the [`run_until_stalled`](https://docs.pybricks.com/en/latest/pupdevices/motor.html#pybricks.pupdevices.Motor.run_until_stalled) + Try experimenting with the [run_until_stalled](https://docs.pybricks.com/en/latest/pupdevices/motor.html#pybricks.pupdevices.Motor.run_until_stalled) method. This can speed up the build process. - Speaking of increasing speed, how fast can you make it? Optimize this robot and set a new world record!