Skip to content
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.

Sign up for GitHub

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

Fix typos in contractions of “it is” #277

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typos in contractions of “it is” #277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions book/data-locality.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -509,7 +509,7 @@ something like this:

^code particles-is-active

We give `Particle` a flag to track whether its in use or not. In the update
We give `Particle` a flag to track whether it's in use or not. In the update
loop, we <span name="branch">check</span> that for each particle. That loads the
flag into the cache along with all of that particle's other data. If the
particle *isn't* active, then we skip over it to the next one. The rest
Expand Down Expand Up @@ -615,7 +615,7 @@ particle system that will be spawning and killing particles anyway.

OK, this is the last example of a simple technique for making your cache
happier. Say we've got an AI component for some game entity. It has some state
in it -- the animation it's currently playing, a goal position its heading
in it -- the animation it's currently playing, a goal position it’s heading
towards, energy level, etc. -- stuff it checks and tweaks every single frame.
Something like:

Expand Down