Fix connections

1 files changed, 3 insertions, 3 deletions

diff --git a/Add-a-new-map-and-landmark.md b/Add-a-new-map-and-landmark.md
index 386b14e..fa8535b 100644
--- a/Add-a-new-map-and-landmark.md
+++ b/Add-a-new-map-and-landmark.md
@@ -304,10 +304,10 @@ Edit [data/maps/attributes.asm](../blob/master/data/maps/attributes.asm):
 +	map_attributes GoldenrodCity, GOLDENROD_CITY, $35, NORTH | SOUTH | WEST
  	connection north, Route35, ROUTE_35, 5
  	connection south, Route34, ROUTE_34, 5
-+	connection west, GlobalTerminalOutside, GLOBAL_TERMINAL_OUTSIDE, -2
++	connection west, GlobalTerminalOutside, GLOBAL_TERMINAL_OUTSIDE, 2
 +
 +	map_attributes GlobalTerminalOutside, GLOBAL_TERMINAL_OUTSIDE, $35, EAST
-+	connection east, GoldenrodCity, GOLDENROD_CITY, 2
++	connection east, GoldenrodCity, GOLDENROD_CITY, -2
 
  ...
 
@@ -324,7 +324,7 @@ The **connections** value is a combination of `NORTH`, `SOUTH`, `WEST`, or `EAST
 
 The `connection` macro takes four arguments: the direction, map name, map ID, and sideways offset. Again, the direction, map name, and map ID are just for identification. The **sideways offset** is how many blocks to shift the connected map perpendicular to its direction. A north or south connection gets shifted right/east, a west or east connection gets shifted down/south. (So negative offsets will shift left/west or up/north, respectively.)
 
-If the offset isn't clear, try comparing screenshots of other maps with their own offset values, and base your own connections on similarly aligned ones. In this case, `GLOBAL_TERMINAL_OUTSIDE` is two blocks lower than `GOLDENROD_CITY`, so their offsets are 2 and −2 respecitvely.
+If the offset isn't clear, try comparing screenshots of other maps with their own offset values, and base your own connections on similarly aligned ones. In this case, `GLOBAL_TERMINAL_OUTSIDE` is two blocks lower than `GOLDENROD_CITY`, so their offsets are −2 and 2 respecitvely.
 
 (Before November 10, 2018, the `connection` macro took six parameters; instead of a single sideways offset, you had to specify a target offset, source offset, and strip length, which were confusing and harder to calculate. The current macro definition has legacy support for the old one, since in all of the official maps, sideways offset = target offset − source offset, with the strip length being completely redundant. I strongly recommend porting the new macro to any old pokecrystal projects.)