docs: Fix broken links and formatting issues in documentation (#1396)

Author: nakamura-to

docs/config.md

@@ -14,7 +14,7 @@ the `org.seasar.doma.jdbc.Config` interface.
 Return a JDBC `DataSource` from the `getDataSource` method.
 If you need to use local transactions provided by Doma, return a `LocalTransactionDataSource`.
 
-See also: [](transaction.md)
+See also: [Transaction](transaction.md)
 
 :::{note}
 This is a required configuration item.
@@ -147,7 +147,7 @@ The default MapKeyNaming does nothing.
 Return a `LocalTransactionManager` from the `getTransactionManager` method.
 By default, the `getTransactionManager` method throws `UnsupportedOperationException`.
 
-See also: [](transaction.md)
+See also: [Transaction](transaction.md)
 
 ### Adding SQL identifiers to SQLs as comments
 
@@ -172,23 +172,23 @@ For example, the QueryImplementors provides a hook to rewrite SQL statements.
 ### Query timeout
 
 Return the query timeout (in seconds) from the `getQueryTimeout` method.
-This value is used as the default in [](query/index.md).
+This value is used as the default in [Queries](query/index.md).
 
 ### Max rows
 
 Return the max rows from the `getMaxRows` method.
-This value is used as the default in [](query/select.md).
+This value is used as the default in [Select](query/select.md).
 
 ### Fetch size
 
 Return the fetch size from the `getFetchSize` method.
-This value is used as the default in [](query/select.md).
+This value is used as the default in [Select](query/select.md).
 
 ### Batch size
 
 Return the batch size from the `getBatchSize` method.
-This value is used as the default in [](query/batch-insert.md),
-[](query/batch-update.md) and [](query/batch-delete.md).
+This value is used as the default in [Batch insert](query/batch-insert.md),
+[Batch update](query/batch-update.md) and [Batch delete](query/batch-delete.md).
 
 ### Providing entity listeners
 

docs/criteria-api.md

@@ -7,7 +7,7 @@
 ## Introduction
 
 :::{warning}
-Please use the Query DSL introduced on the [](query-dsl.md) page instead of the Entityql and NativeSql
+Please use the Query DSL introduced on the [Unified Criteria API](query-dsl.md) page instead of the Entityql and NativeSql
 DSLs explained here.
 The Query DSL is a new, unified interface that combines both Entityql and NativeSql DSLs.
 :::
@@ -105,7 +105,7 @@ These metamodels allow you to make your query typesafe.
 You can customize the name of the metamodels by the Metamodel annotation elements.
 
 To customize all metamodels in bulk, you can use the annotation processor options.
-See [](annotation-processing.md) and check the following options:
+See [Annotation Processing](annotation-processing.md) and check the following options:
 
 - doma.metamodel.enabled
 - doma.metamodel.prefix
@@ -1157,7 +1157,7 @@ order by
 
 ## Delete statement
 
-For the specification of the where expression, see [](#criteria-where).
+For the specification of the where expression, see [Criteria Where](#criteria-where).
 The same rule is applied to delete statements.
 
 ### Delete settings (Entityql, NativeSql)
@@ -1468,7 +1468,7 @@ int count result = nativeSql
 
 ## Update statement
 
-For the specification of the where expression, see [](#criteria-where).
+For the specification of the where expression, see [Criteria Where](#criteria-where).
 The same rule is applied to update statements.
 
 ### Update settings (Entityql, NativeSql)

docs/dao.md

@@ -14,9 +14,9 @@ Implementation classes for the DAO interfaces are automatically generated by the
 
 ## Query definition
 
-[](query/index.md) can be defined using annotations.
+[Queries](query/index.md) can be defined using annotations.
 
-You can use [](query-builder/index.md) or [](query-dsl.md) in a [](#dao-default-method) when you need to build queries dynamically in Java code.
+You can use [Query builders](query-builder/index.md) or [Unified Criteria API](query-dsl.md) in a [Dao Default Method](#dao-default-method) when you need to build queries dynamically in Java code.
 
 (dao-default-method)=
 
@@ -52,7 +52,7 @@ Employee employee = employeeDao.selectById(1);
 ```
 
 By default, the implementation class name is the interface name suffixed with `Impl`.
-Please refer to [](annotation-processing.md) for information on how to customize the package name and suffix.
+Please refer to [Annotation Processing](annotation-processing.md) for information on how to customize the package name and suffix.
 
 A DAO interface does not need to be defined in a one-to-one relationship with an entity class.
 One DAO interface can handle multiple entity classes.

docs/domain.md

@@ -15,7 +15,7 @@ Every domain class is either an internal domain class or an external domain clas
 
 Internal domain classes must be annotated with `@Domain`.
 The `valueType` element of the `@Domain` annotation specifies the data type of the corresponding database column.
-You must specify a type from [](basic.md) for the `valueType` element.
+You must specify a type from [Basic classes](basic.md) for the `valueType` element.
 
 ### Instantiation with a constructor
 

docs/embeddable.md

@@ -79,9 +79,9 @@ By default, all fields are persistent and correspond to database columns or resu
 
 The field type must be one of the following:
 
-- [](basic.md)
-- [](domain.md)
-- java.util.Optional, whose element is either [](basic.md) or [](domain.md)
+- [Basic classes](basic.md)
+- [Domain classes](domain.md)
+- java.util.Optional, whose element is either [Basic classes](basic.md) or [Domain classes](domain.md)
 - java.util.OptionalInt
 - java.util.OptionalLong
 - java.util.OptionalDouble

docs/entity.md

@@ -130,18 +130,18 @@ public class Employee {
 }
 ```
 
-If the `@Table` annotation is not specified, the table name is determined by the [](#naming-convention) .
+If the `@Table` annotation is not specified, the table name is determined by the [Naming Convention](#naming-convention) .
 
 ## Field definition
 
 By default, all fields in an entity class are persistent and correspond to database columns or result set columns.
 
 The field type must be one of the following:
 
-- [](basic.md)
-- [](domain.md)
-- [](embeddable.md)
-- java.util.Optional, whose element is either [](basic.md) or [](domain.md)
+- [Basic classes](basic.md)
+- [Domain classes](domain.md)
+- [Embeddable classes](embeddable.md)
+- java.util.Optional, whose element is either [Basic classes](basic.md) or [Domain classes](domain.md)
 - java.util.OptionalInt
 - java.util.OptionalLong
 - java.util.OptionalDouble
@@ -173,10 +173,10 @@ properties to `false` within the `@Column` annotation:
 String employeeName;
 ```
 
-If the `@Column` annotation is not specified, the column name is determined by the [](#naming-convention) .
+If the `@Column` annotation is not specified, the column name is determined by the [Naming Convention](#naming-convention) .
 
 :::{note}
-When the field type is [](embeddable.md), you cannot apply the `@Column` annotation to the field.
+When the field type is [Embeddable classes](embeddable.md), you cannot apply the `@Column` annotation to the field.
 :::
 
 ### Id
@@ -199,7 +199,7 @@ Integer id2;
 ```
 
 :::{note}
-When the field type is [](embeddable.md), you cannot apply the `@Id` annotation to the field.
+When the field type is [Embeddable classes](embeddable.md), you cannot apply the `@Id` annotation to the field.
 :::
 
 (identity-auto-generation)=
@@ -211,7 +211,7 @@ You can instruct Doma to generate id values automatically using the `@GeneratedV
 The field type must be one of the following:
 
 - the subclass of java.lang.Number
-- [](domain.md), whose value type is the subclass of java.lang.Number
+- [Domain classes](domain.md), whose value type is the subclass of java.lang.Number
 - java.util.Optional, whose element is either above types
 - OptionalInt
 - OptionalLong
@@ -291,7 +291,7 @@ The version fields for optimistic locking are represented with the `@Version` an
 The field type must be one of the following:
 
 - the subclass of java.lang.Number
-- [](domain.md), whose value type is the subclass of java.lang.Number
+- [Domain classes](domain.md), whose value type is the subclass of java.lang.Number
 - java.util.Optional, whose element is either above types
 - OptionalInt
 - OptionalLong
@@ -304,7 +304,7 @@ Integer version;
 ```
 
 :::{note}
-When the field type is [](embeddable.md), you cannot apply the `@Version` annotation to the field.
+When the field type is [Embeddable classes](embeddable.md), you cannot apply the `@Version` annotation to the field.
 :::
 
 ### Tenant Id
@@ -318,7 +318,7 @@ String tenantId;
 ```
 
 :::{note}
-When the field type is [](embeddable.md), you cannot apply the `@TenantId` annotation to the field.
+When the field type is [Embeddable classes](embeddable.md), you cannot apply the `@TenantId` annotation to the field.
 :::
 
 ### Transient
@@ -349,7 +349,7 @@ Instead, this annotation is used to define entity relationships within an aggreg
 
 This annotation should be used in conjunction with the aggregate strategy,
 ensuring that related entities are treated as a single unit of consistency.
-For more details, see [](aggregate-strategy.md).
+For more details, see [Aggregate strategies](aggregate-strategy.md).
 
 ### OriginalStates
 

docs/faq.md

@@ -78,7 +78,7 @@ You may get the following message, though the file exists:
 
 You can avoid this error by configuring recommended settings for each build tool and IDE.
 
-See [](build.md).
+See [Building an application](build.md).
 
 ### Do you provide a tool to generate Java code from a database schema?
 
@@ -107,14 +107,14 @@ There are two ways:
 - SQL Templates.
 - The Criteria API.
 
-See [](sql.md) and [](query-dsl.md) for detailed information.
+See [SQL templates](sql.md) and [Unified Criteria API](query-dsl.md) for detailed information.
 
 ### Does Doma support fetching relationships such as one-to-one or one-to-many?
 
 Yes, there are two ways to fetch relationships:
 
-- [](aggregate-strategy.md) with SQL Templates.
-- [](query-dsl.md#association) with the Criteria API.
+- [Aggregate strategies](aggregate-strategy.md) with SQL Templates.
+- [Association](query-dsl.md#association) with the Criteria API.
 
 ### Does Doma provide a JDBC connection pooling feature?
 

docs/getting-started.md

@@ -73,7 +73,7 @@ standard SQL for insert, update, and delete operations and for writing complex S
 ## DSL style
 
 In the DSL style, you work with examples in the `boilerplate.java17.repository.EmployeeRepository`
-and the [](query-dsl.md) for operations.
+and the [Unified Criteria API](query-dsl.md) for operations.
 
 ### SELECT
 
@@ -132,7 +132,7 @@ public void update(Employee employee) {
 ## DAO style
 
 You can find some examples in `boilerplate.java17.dao.EmployeeDao`.
-See [](dao.md) and [](sql.md) for more information.
+See [DAO interfaces](dao.md) and [SQL templates](sql.md) for more information.
 
 ### SELECT (DAO)
 

docs/kotlin-support.md

@@ -94,7 +94,7 @@ It is recommended to use the Kotlin-specific Criteria API rather than DAO interf
 :::
 
 Doma provides `KQueryDsl`, a Criteria API specifically designed for Kotlin.
-It is very similar to the `QueryDsl`, which is described in [](query-dsl.md).
+It is very similar to the `QueryDsl`, which is described in [Unified Criteria API](query-dsl.md).
 The main advantage of `KQueryDsl` is its simplicity.
 
 ```kotlin
@@ -128,7 +128,7 @@ dependencies {
 
 ### Code Generation
 
-Use [](codegen.md).
+Use [Doma CodeGen Plugin](codegen.md).
 This plugin supports Kotlin code generation.
 
 ### Using kapt in Gradle

docs/locale/ja/LC_MESSAGES/annotation-processing.po

@@ -27,8 +27,8 @@ msgid ""
 "Doma uses the [Pluggable Annotation Processing "
 "API](https://www.jcp.org/en/jsr/detail?id=269) at compile time."
 msgstr ""
-"Doma はコンパイル時に `Pluggable Annotation Processing API "
-"<https://www.jcp.org/en/jsr/detail?id=269>`_ を使用します。"
+"Doma はコンパイル時に `[Pluggable Annotation Processing API "
+"](https://www.jcp.org/en/jsr/detail?id=269) を使用します。"
 
 #: ../../annotation-processing.md:9
 msgid ""
@@ -252,8 +252,8 @@ msgid ""
 "Use [the compilerArgs "
 "property](https://docs.gradle.org/current/dsl/org.gradle.api.tasks.compile.CompileOptions.html#org.gradle.api.tasks.compile.CompileOptions:compilerArgs):"
 msgstr ""
-"`compilerArgs プロパティ "
-"<https://docs.gradle.org/current/dsl/org.gradle.api.tasks.compile.CompileOptions.html#org.gradle.api.tasks.compile.CompileOptions:compilerArgs>`_"
+"[compilerArgs プロパティ]("
+"https://docs.gradle.org/current/dsl/org.gradle.api.tasks.compile.CompileOptions.html#org.gradle.api.tasks.compile.CompileOptions:compilerArgs)"
 " を使用します。"
 
 #: ../../annotation-processing.md
@@ -273,8 +273,8 @@ msgid ""
 "Use [the compilerArgs parameter](https://maven.apache.org/plugins/maven-"
 "compiler-plugin/examples/pass-compiler-arguments.html):"
 msgstr ""
-"`compilerArgs パラメータ <https://maven.apache.org/plugins/maven-compiler-"
-"plugin/examples/pass-compiler-arguments.html>`_: を使用します。"
+"[compilerArgs パラメータ](https://maven.apache.org/plugins/maven-compiler-"
+"plugin/examples/pass-compiler-arguments.html): を使用します。"
 
 #: ../../annotation-processing.md:167
 msgid "Setting Options in Eclipse"
@@ -290,8 +290,8 @@ msgid ""
 "[com.diffplug.eclipse.apt](https://plugins.gradle.org/plugin/com.diffplug.eclipse.apt)"
 " and the `processorArgs` property:"
 msgstr ""
-"Gradle プラグイン `com.diffplug.eclipse.apt "
-"<https://plugins.gradle.org/plugin/com.diffplug.eclipse.apt>`_ と "
+"Gradle プラグイン [com.diffplug.eclipse.apt]"
+"(https://plugins.gradle.org/plugin/com.diffplug.eclipse.apt) と "
 "`processorArgs` プロパティを使用します。"
 
 #: ../../annotation-processing.md:212