From e2c7196ea87fdf827f36323342500e963eb40273 Mon Sep 17 00:00:00 2001 From: David Komer Date: Thu, 16 Nov 2017 18:51:35 +0200 Subject: [PATCH] tutorial docs (#4492) --- docs/source/Tutorial.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/Tutorial.md b/docs/source/Tutorial.md index 83e49bb7e..01d05933d 100644 --- a/docs/source/Tutorial.md +++ b/docs/source/Tutorial.md @@ -840,7 +840,7 @@ for the `path` field above:
~~~{.py} - MyGame.Example.Monster.MonsterStartPathVector(builder, 2) + MyGame.Sample.Monster.MonsterStartPathVector(builder, 2) MyGame.Sample.Vec3.CreateVec3(builder, 1.0, 2.0, 3.0) MyGame.Sample.Vec3.CreateVec3(builder, 4.0, 5.0, 6.0) path = builder.EndVector(2) @@ -848,7 +848,7 @@ for the `path` field above:
~~~{.js} - MyGame.Example.Monster.startPathVector(builder, 2); + MyGame.Sample.Monster.startPathVector(builder, 2); MyGame.Sample.Vec3.createVec3(builder, 1.0, 2.0, 3.0); MyGame.Sample.Vec3.createVec3(builder, 4.0, 5.0, 6.0); var path = builder.endVector(); @@ -1166,7 +1166,7 @@ appropriate `finish` method.
~~~{.js} // Call `finish()` to instruct the builder that this monster is complete. - builder.finish(orc); // You could also call `MyGame.Example.Monster.finishMonsterBuffer(builder, + builder.finish(orc); // You could also call `MyGame.Sample.Monster.finishMonsterBuffer(builder, // orc);`. ~~~