Skip to content

Commit

Permalink
fix some typos
Browse files Browse the repository at this point in the history
  • Loading branch information
jaredlll08 committed Jul 29, 2022
1 parent 1e2962b commit cbd3595
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

// As we have explained previously, to create something we all need a factory. The sound event factory can be obtained
// unsurprisingly through `<factory:sound_event>`.
// The factory exposes us a single method to create an event, asking us for an ID. The ID is a string that identifies
// The factory exposes to us a single method to create an event, asking us for an ID. The ID is a string that identifies
// the name we want to give to the event. It has to follow all resource location conventions.
// Last but not least, we have to `build` the created sound event. This will give us a reference to use later.
// Let me now show you some commented examples.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
// ContentTweaker let's you create many different types of items, and allows CraftTweaker addons to provide additional
// personalization options. For this reason, creating items is slightly less straight-forward than the previous two
// examples and requires you to specify a "type".
// The "type" of an item essentially represents what kind of things the items is supposed to do and what data is
// The "type" of an item essentially represents what kind of things the item is supposed to do and what data is
// required for it to behave correctly. Each "type" might require different information, so you have to look at the
// documentation for the type you desire.
// In this script, we will only be dealing with basic item types, meaning items that have no special behavior except for
Expand Down

0 comments on commit cbd3595

Please sign in to comment.