Yoast - Yoast SEO Premium (for WordPress) - en to en_CA translation catalogue (19 entries)

en: Keep your site well-organised so people won't get lost
en_CA: Keep your site well organised so people won't get lost

en: Optimize your content further with our smart analysis
en_CA: Optimise your content further with our smart analysis

en: Rank with articles you want to rank with
en_CA: Rank with articles with which you want to rank

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: E.g. %1$sAcme inc%2$s
en_CA: Eg %1$sAcme inc%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: E.g. %1$ssoftware engineer%2$s
en_CA: Eg %1$ssoftware engineer%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: Comma separated, e.g. %1$sEnglish, French, Dutch%2$s
en_CA: Comma separated, eg %1$sEnglish, French, Dutch%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: Comma separated, e.g. %1$sPHP, JavaScript, 90's rock music%2$s
en_CA: Comma separated, eg %1$sPHP, JavaScript, 90's rock music%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: Comma separated, e.g. %1$sMost likely to succeed - 1991, Smartest in class - 1990%2$s
en_CA: Comma separated, eg %1$sMost likely to succeed – 1991, Smartest in class – 1990%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: E.g. %1$sfemale%2$s, %1$smale%2$s, %1$snon-binary%2$s
en_CA: Eg %1$sfemale%2$s, %1$smale%2$s, %1$snon-binary%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: Use format: %1$sYYYY-MM-DD%2$s
en_CA: Use format: %1$sDD-MM-YYYY%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: E.g. %1$sMD%2$s, %1$sPhD%2$s
en_CA: Eg %1$sMD%2$s, %1$sPhD%2$s

note: translators: %1$s is replaced by `<code>`, %2$s by `</code>`.
en: E.g. %1$sDr%2$s, %1$sMs%2$s, %1$sMr%2$s
en_CA: Eg %1$sDr%2$s, %1$sMs%2$s, %1$sMr%2$s

en: As you're on Nginx, you should add the following include to the Nginx config file:
en_CA: As you're on Nginx, you should add the following include to the NGINX config file:

note: translators: %1$s expands to the returned http code
en: The URL you are redirecting to seems to return a %1$s status. You might want to check if the target can be reached manually before saving.
en_CA: The url you are redirecting seems to return a %1$s status. You might want to check if the target can be reached manually before saving.

en: You're redirecting to a target that returns a 301 HTTP code (permanently moved). Make sure the target you specify is directly reachable.
en_CA: You\'re redirecting to a target that returns a 301 HTTP code (permanently moved). Make sure the target you specify is directly reachable.

en: The old URL already exists as a redirect.
en_CA: The old url already exists as a redirect.

en: Redirect it to another URL
en_CA: Redirect it to another URL.

en: Make it serve a 410 Content Deleted header
en_CA: Make it serve a 410 Content Deleted header.

note: translators: 1: opens a link to a related help center article. 2: closes the link.
en: Regular Expression (regex) Redirects are extremely powerful redirects. You should only use them if you know what you are doing. %1$sRead more about regex redirects on our help center%2$s.
en_CA: Regular Expression (regex) Redirects are extremely powerful redirects. You should only use them if you know what you are doing. %1$sRead more about regex redirects on our knowledge base%2$s.
