[from now] 2012/06/29 23:14:05

diff --git a/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc b/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
index f6ff503..32eb187 100644
--- a/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
+++ b/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
@@ -1,4 +1,4 @@
-A many-to-one relationship is the simplest kind, and is defined with a property of the type of another domain class. Consider this example:
+多対1の関連は、最も単純な種類であり、別のドメインクラスの型のプロパティで定義します。次の例を考えてみましょう。{hidden}A many-to-one relationship is the simplest kind, and is defined with a property of the type of another domain class. Consider this example:{hidden}

 h5. Example A
[from now] 2012/06/29 23:51:06

diff --git a/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc b/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
index 32eb187..5d6f570 100644
--- a/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
+++ b/guide/GORM/domainClasses/gormAssociation/manyToOneAndOneToOne.gdoc
@@ -13,7 +13,7 @@ class Nose {
 }
 {code}

-In this case we have a unidirectional many-to-one relationship from @Face@ to @Nose@. To make this relationship bidirectional define the other side as follows:
+このケースでは @Face@ から @Nose@ へ一方向の many-to-one の関連を持ちます。これを双方向となるように定義するには次のようにします:{hidden}In this case we have a unidirectional many-to-one relationship from @Face@ to @Nose@. To make this relationship bidirectional define the other side as follows:{hidden}

 h5. Example B

@@ -29,19 +29,20 @@ class Nose {
 }
 {code}

-In this case we use the @belongsTo@ setting to say that @Nose@ "belongs to" @Face@. The result of this is that we can create a @Face@, attach a @Nose@ instance to it and when we save or delete the @Face@ instance, GORM will save or delete the @Nose@. In other words, saves and deletes will cascade from @Face@ to the associated @Nose@:
+このケースでは @belongsTo@ を使用して @Nose@ "belongs to" @Face@ であることを設定しています。このように設定することで @Face@ 作成し @Node@ を設定することで @Face@ インタンスを save したり delete すると GROM は @Nose@ も save もしくは delete します。言い方を変えると保存、削除は @Face@ から関連した @Face@ へカスケードされます:
+{hidden}In this case we use the @belongsTo@ setting to say that @Nose@ "belongs to" @Face@. The result of this is that we can create a @Face@, attach a @Nose@ instance to it and when we save or delete the @Face@ instance, GORM will save or delete the @Nose@. In other words, saves and deletes will cascade from @Face@ to the associated @Nose@:{hidden}

 {code}
 new Face(nose:new Nose()).save()
 {code}

-The example above will save both face and nose. Note that the inverse _is not_ true and will result in an error due to a transient @Face@:
+上記の例ではfaceとnose両方が保存されます。逆にした場合はエラーになることに注意してください:{hidden}The example above will save both face and nose. Note that the inverse _is not_ true and will result in an error due to a transient @Face@:{hidden}

 {code}
 new Nose(face:new Face()).save() // will cause an error
 {code}

-Now if we delete the @Face@ instance, the @Nose@ will go too:
+もし @Face@ インスタンスを削除したい場合、@Nose@も削除されます。{hidden}Now if we delete the @Face@ instance, the @Nose@ will go too:{hidden}

 {code}
 def f = Face.get(1)