@@ -181,11 +181,11 @@ public static IQueryable<DateTimeOffset> AsQueryableValues(this DbContext dbCont
181181 /// </summary>
182182 /// <param name="dbContext">The <see cref="DbContext"/> owning the query.</param>
183183 /// <param name="values">The sequence of values to compose.</param>
184- /// <param name="isUnicode">If <c> true</c >, will cast the <paramref name="values"/> as <c>nvarchar</c>, otherwise, <c>varchar</c>.</param>
184+ /// <param name="isUnicode">If <see langword=" true"/ >, will cast the <paramref name="values"/> as <c>nvarchar</c>, otherwise, <c>varchar</c>.</param>
185185 /// <returns>An <see cref="IQueryable{Char}">IQueryable<char></see> that can be composed with other entities in the query.</returns>
186186 /// <remarks>
187187 /// About Performance: If the result is going to be composed against the property of an entity that uses
188- /// unicode (<c>nvarchar</c>), then <paramref name="isUnicode"/> should be <c> true</c >.
188+ /// unicode (<c>nvarchar</c>), then <paramref name="isUnicode"/> should be <see langword=" true"/ >.
189189 /// Failing to do this may force SQL Server's query engine to do an implicit casting, which results
190190 /// in a scan instead of an index seek (assuming there's a covering index).
191191 /// </remarks>
@@ -202,11 +202,11 @@ public static IQueryable<char> AsQueryableValues(this DbContext dbContext, IEnum
202202 /// </summary>
203203 /// <param name="dbContext">The <see cref="DbContext"/> owning the query.</param>
204204 /// <param name="values">The sequence of values to compose.</param>
205- /// <param name="isUnicode">If <c> true</c >, will cast the <paramref name="values"/> as <c>nvarchar</c>, otherwise, <c>varchar</c>.</param>
205+ /// <param name="isUnicode">If <see langword=" true"/ >, will cast the <paramref name="values"/> as <c>nvarchar</c>, otherwise, <c>varchar</c>.</param>
206206 /// <returns>An <see cref="IQueryable{String}">IQueryable<string></see> that can be composed with other entities in the query.</returns>
207207 /// <remarks>
208208 /// About Performance: If the result is going to be composed against the property of an entity that uses
209- /// unicode (<c>nvarchar</c>), then <paramref name="isUnicode"/> should be <c> true</c >.
209+ /// unicode (<c>nvarchar</c>), then <paramref name="isUnicode"/> should be <see langword=" true"/ >.
210210 /// Failing to do this may force SQL Server's query engine to do an implicit casting, which results
211211 /// in a scan instead of an index seek (assuming there's a covering index).
212212 /// </remarks>
0 commit comments