Replace 'e.g.' with 'for example' in documentation and comments
Closes gh-33515
This commit is contained in:
Yanming Zhou
committed by
Sam Brannen
Sam Brannen
parent
e55fe9077f
commit
8941e2876e
@@ -42,7 +42,7 @@ public interface JCacheConfigurer extends CachingConfigurer {
|
||||
/**
|
||||
* Return the {@link CacheResolver} bean to use to resolve exception caches for
|
||||
* annotation-driven cache management. Implementations must explicitly declare
|
||||
* {@link org.springframework.context.annotation.Bean @Bean}, e.g.
|
||||
* {@link org.springframework.context.annotation.Bean @Bean}, for example,
|
||||
* <pre class="code">
|
||||
* @Configuration
|
||||
* @EnableCaching
|
||||
|
||||
@@ -484,7 +484,7 @@ public class JavaMailSenderImpl implements JavaMailSender {
|
||||
/**
|
||||
* Obtain a Transport object from the given JavaMail Session,
|
||||
* using the configured protocol.
|
||||
* <p>Can be overridden in subclasses, e.g. to return a mock Transport object.
|
||||
* <p>Can be overridden in subclasses, for example, to return a mock Transport object.
|
||||
* @see jakarta.mail.Session#getTransport(String)
|
||||
* @see #getSession()
|
||||
* @see #getProtocol()
|
||||
|
||||
@@ -897,7 +897,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@link #setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param dataSource the {@code jakarta.activation.DataSource} to take
|
||||
* the content from, determining the InputStream and the content type
|
||||
@@ -919,7 +919,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@link #setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param inlineFilename the fileName to use for the inline element's part
|
||||
* @param dataSource the {@code jakarta.activation.DataSource} to take
|
||||
@@ -959,7 +959,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@link #setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param file the File resource to take the content from
|
||||
* @throws MessagingException in case of errors
|
||||
@@ -986,7 +986,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@link #setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param resource the resource to take the content from
|
||||
* @throws MessagingException in case of errors
|
||||
@@ -1013,7 +1013,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@code setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param inputStreamSource the resource to take the content from
|
||||
* @param contentType the content type to use for the element
|
||||
@@ -1042,7 +1042,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@code setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param inlineFilename the file name to use for the inline element
|
||||
* @param inputStreamSource the resource to take the content from
|
||||
@@ -1072,7 +1072,7 @@ public class MimeMessageHelper {
|
||||
* <p><b>NOTE:</b> Invoke {@code addInline} <i>after</i> {@code setText};
|
||||
* else, mail readers might not be able to resolve inline references correctly.
|
||||
* @param contentId the content ID to use. Will end up as "Content-ID" header
|
||||
* in the body part, surrounded by angle brackets: e.g. "myId" → "<myId>".
|
||||
* in the body part, surrounded by angle brackets: for example, "myId" → "<myId>".
|
||||
* Can be referenced in HTML source via src="cid:myId" expressions.
|
||||
* @param inlineFilename the fileName to use for the inline element's part
|
||||
* @param inputStreamSource the resource to take the content from
|
||||
|
||||
@@ -54,7 +54,7 @@ public class SchedulerAccessorBean extends SchedulerAccessor implements BeanFact
|
||||
* Specify the Quartz {@link Scheduler} to operate on via its scheduler name in the Spring
|
||||
* application context or also in the Quartz {@link org.quartz.impl.SchedulerRepository}.
|
||||
* <p>Schedulers can be registered in the repository through custom bootstrapping,
|
||||
* e.g. via the {@link org.quartz.impl.StdSchedulerFactory} or
|
||||
* for example, via the {@link org.quartz.impl.StdSchedulerFactory} or
|
||||
* {@link org.quartz.impl.DirectSchedulerFactory} factory classes.
|
||||
* However, in general, it's preferable to use Spring's {@link SchedulerFactoryBean}
|
||||
* which includes the job/trigger/listener capabilities of this accessor as well.
|
||||
|
||||
@@ -319,7 +319,7 @@ public class SchedulerFactoryBean extends SchedulerAccessor implements FactoryBe
|
||||
* It is therefore strongly recommended to perform all operations on
|
||||
* the Scheduler within Spring-managed (or plain JTA) transactions.
|
||||
* Else, database locking will not properly work and might even break
|
||||
* (e.g. if trying to obtain a lock on Oracle without a transaction).
|
||||
* (for example, if trying to obtain a lock on Oracle without a transaction).
|
||||
* <p>Supports both transactional and non-transactional DataSource access.
|
||||
* With a non-XA DataSource and local Spring transactions, a single DataSource
|
||||
* argument is sufficient. In case of an XA DataSource and global JTA transactions,
|
||||
|
||||
@@ -262,7 +262,7 @@ application/astound asn
|
||||
|
||||
# SPECIAL EMBEDDED OBJECT
|
||||
|
||||
# OLE script e.g. Visual Basic (Ncompass)
|
||||
# OLE script, for example, Visual Basic (Ncompass)
|
||||
application/x-olescript axs
|
||||
# OLE Object (Microsoft/NCompass)
|
||||
application/x-oleobject ods
|
||||
|
||||
Reference in New Issue
Block a user