Skip to content

Commit 1028e73

Browse files
authored
[Docs] : Fix typos (#1095)
* Update index.md * Update predator_prey.jl * Update optim.jl * Update event_rock_paper_scissors.jl
1 parent 6707135 commit 1028e73

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

docs/src/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ This is an example of emergent behavior from simple interactions of agents that
123123

124124
## Getting help
125125

126-
You're looking for support for Agents.jl? Look no further! Here's some things you can do to resolve your questions about Agents.jl:
126+
You're looking for support for Agents.jl? Look no further! Here are some things you can do to resolve your questions about Agents.jl:
127127

128128
1. Read the online documentation! It is likely that the thing you want to know is already documented, so use the search bar and search away!
129129
2. Chat with us in the channel `#dynamics-bridged` in the [Julia Slack](https://julialang.org/slack/)!

examples/event_rock_paper_scissors.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ end
120120
# Another way to think of propensities is the relative probability mass
121121
# for an event to happen.
122122
# The propensities may be constants or functions of the
123-
# currently actived agent and the model.
123+
# currently active agent and the model.
124124

125125
# Here, the propensities for moving and attacking will be constants,
126126
attack_propensity = 1.0

examples/optim.jl

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# # Optimizing agent based models
22

33
# Sometimes we need to fine-tune our ABMs parameters to a specific outcome.
4-
# The brute-force solution can quickly become infeasible for even for a few different
4+
# The brute-force solution can quickly become infeasible even for a few different
55
# parameter settings over a number of valid scan ranges. Most of the time,
66
# ABMs are also stochastic, so the effect of a parameter setting should be derived from
77
# taking the average value only after running the model several times.
@@ -23,7 +23,7 @@
2323
# To look for optimal parameters, we need to define a cost function.
2424
# The cost function takes as arguments the model parameters that we want to tune;
2525
# in a SIR model, that would be the migration rate, death rate, transmission rate,
26-
# when an infected person has been detected (`β_det`), or when the remain undetected
26+
# when an infected person has been detected (`β_det`), or when they remain undetected
2727
# (`β_und`), infection period, reinfection probability, and time until the infection
2828
# is detected. The function returns an *objective*: this value takes the form one
2929
# or more numbers, which the optimiser will attempt to minimize.

examples/predator_prey.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@
4343
# First we define the agent types
4444
# (here you can see that it isn't really that much
4545
# of an advantage to have two different agent types. Like in the [Rabbit, Fox, Wolf](@ref)
46-
# example, we could have only one type and one additional filed to separate them.
46+
# example, we could have only one type and one additional field to separate them.
4747
# Nevertheless, for the sake of example, we will use two different types.)
4848
using Agents, Random
4949

0 commit comments

Comments
 (0)