replace AMO with SITE_NAME in policy

1 files changed, 13 insertions, 13 deletions

diff --git a/site/app/locale/en_US/pages/policy.thtml b/site/app/locale/en_US/pages/policy.thtml
index aeceb48..b4d8d34 100644
--- a/site/app/locale/en_US/pages/policy.thtml
+++ b/site/app/locale/en_US/pages/policy.thtml
@@ -4,13 +4,13 @@
 <p>See the %s.</p>
 
 <h2>What add-ons are in the sandbox?</h2>
-<p>The sandbox is where all add-ons that are hosted on AMO go, to start. It contains new versions of public add-ons, as well as all versions for add-ons that are not made public. When a new add-on, or an update to an existing add-on, is submitted to AMO, it is placed in the sandbox.</p>
+<p>The sandbox is where all add-ons that are hosted on <?=SITE_NAME?> go, to start. It contains new versions of public add-ons, as well as all versions for add-ons that are not made public. When a new add-on, or an update to an existing add-on, is submitted to <?=SITE_NAME?>, it is placed in the sandbox.</p>
 
 <p>Some add-ons, and their specific versions, are made public after the review process indicates that they are ready and appropriate for public display. Other add-ons will remain in the sandbox indefinitely, where they are available to users who choose to browse the sandbox list and experiment with the software there.</p>
 
 <h2>How do add-ons become public?</h2>
 
-<p>Add-ons are reviewed by AMO users who opt into viewing the sandbox and testing the packages found there. The reviews that AMO users write will indicate whether an add-on is sufficiently useful, well-written and polished to be put in front of all of Firefox's users. These reviews, possibly in addition to other reviews and inspections by the AMO team, are used to determine whether a given add-on should be made public, whether it needs more work to be polished for wider visibility, or whether it's not suitable for promotion on the AMO site outside of the sandbox.</p>
+<p>Add-ons are reviewed by <?=SITE_NAME?> users who opt into viewing the sandbox and testing the packages found there. The reviews that <?=SITE_NAME?> users write will indicate whether an add-on is sufficiently useful, well-written and polished to be put in front of all of Firefox's users. These reviews, possibly in addition to other reviews and inspections by the <?=SITE_NAME?> team, are used to determine whether a given add-on should be made public, whether it needs more work to be polished for wider visibility, or whether it's not suitable for promotion on the <?=SITE_NAME?> site outside of the sandbox.</p>
 
 <h2>How do I get my add-on promoted to public status?</h2>
 
@@ -18,11 +18,11 @@
 
 <h2>What are the criteria for public add-ons?</h2>
 
-<p>An add-on that's made public on AMO should be of high quality, and give users an improved web experience. We look for the following things when deciding whether an add-on is appropriate for the public side of AMO:</p>
+<p>An add-on that's made public on <?=SITE_NAME?> should be of high quality, and give users an improved web experience. We look for the following things when deciding whether an add-on is appropriate for the public side of <?=SITE_NAME?>:</p>
 
 <h3>Are you responsive?</h3>
 
-<p>We expect that an author who is promoting their add-on to Firefox's many users is responsive to problem reports, maintains their contact information, and updates their add-on promptly to keep current with Firefox releases and changes in AMO policies. This doesn't mean that you have to reply to every question that someone posts in the discussions, or that you even need to fix every bug, but we do expect that you will respond to issues in a manner that's appropriate to the severity of the issue in question.</p>
+<p>We expect that an author who is promoting their add-on to Firefox's many users is responsive to problem reports, maintains their contact information, and updates their add-on promptly to keep current with Firefox releases and changes in <?=SITE_NAME?> policies. This doesn't mean that you have to reply to every question that someone posts in the discussions, or that you even need to fix every bug, but we do expect that you will respond to issues in a manner that's appropriate to the severity of the issue in question.</p>
 
 <h3>Is the add-on clearly and accurately described?</h3>
 
@@ -32,13 +32,13 @@
 
 <h3>Are all privacy and security concerns clearly spelled out?</h3>
 
-<p>This is an aspect of a clear and accurate description, but such an important one that we feel it deserves specific mention.  Many very useful and well-written add-ons manipulate some form of user data, or can present security hazards if misused; they are welcome on the public portion of AMO, but they must make it very clear to users what risks they might encounter, and what they can do to protect themselves.</p>
+<p>This is an aspect of a clear and accurate description, but such an important one that we feel it deserves specific mention.  Many very useful and well-written add-ons manipulate some form of user data, or can present security hazards if misused; they are welcome on the public portion of <?=SITE_NAME?>, but they must make it very clear to users what risks they might encounter, and what they can do to protect themselves.</p>
 
 <h3>Has the add-on been well-tested, and is it free of obvious or serious defects?</h3>
 
 <p>One important thing that we look for when considering an add-on for public access is whether its sandbox reviews indicate that it has received thorough testing, and that it doesn't have serious problems or negative impacts on the browser.  If reviewers report problems such as major performance issues, crashes, frequent problems using the functions of the add-on, or spamming of messages to the error console, you should take those reports to heart, and re-nominate your add-on after you've addressed them as best you can. We don't expect you to perfectly optimize or have zero bugs -- Firefox itself undergoes constant improvement in these areas -- but we do want you to take reasonable efforts to minimize downsides, and to clearly call out cases where users may be surprised by those that remain.</p>
 
-<p>If your add-on has been tested outside of the AMO Sandbox process, such as by a group of users of your service or an in-house QA team, you should indicate that in your nomination message.  It certainly helps us establish what the level of testing has been, and can help get your add-on up on the site.</p>
+<p>If your add-on has been tested outside of the <?=SITE_NAME?> Sandbox process, such as by a group of users of your service or an in-house QA team, you should indicate that in your nomination message.  It certainly helps us establish what the level of testing has been, and can help get your add-on up on the site.</p>
 
 <h3>Do the add-on and add-on author both treat the user respectfully?</h3>
 
@@ -52,31 +52,31 @@
 
 <p>If your add-on just provides bookmarks or other simple access points to your site, it's probably not
 appropriate for the public part of the site. Like the rest of the Mozilla project, we love web applications and
-new web services, but Firefox add-ons should provide an improved browsing experience for the user and not just be a way to promote a new site or service through an AMO listing.  If the description for your add-on is mostly about the service rather than the improvements it makes to the user's browser experience, you're probably not on the right track.</p>
+new web services, but Firefox add-ons should provide an improved browsing experience for the user and not just be a way to promote a new site or service through an <?=SITE_NAME?> listing.  If the description for your add-on is mostly about the service rather than the improvements it makes to the user's browser experience, you're probably not on the right track.</p>
 
 <h3>Is the add-on free of unlicensed trademarks or copyrights?</h3>
 
-<p>Though you may mean no harm to the holder of a trademark, or the owner of a copyrighted work, we can't host add-ons that infringe on trademarks or copyrights.  If you don't have permission to use a trademarked name or image, please do not submit your add-on to AMO.  If your add-on includes code that is copyrighted by someone else, and is not licensed to you to use in your add-on, please do not submit your add-on to AMO.  (If the holder of a trademark or copyright objects to the use of their trademark, we will very likely have to have the request for removal reviewed by counsel, and we will remove the add-on if it's deemed legally necessary.  This is an expensive process in terms of the project's resources, including time and money, so we ask you to be respectful and not cause us undue difficulty.)</p>
+<p>Though you may mean no harm to the holder of a trademark, or the owner of a copyrighted work, we can't host add-ons that infringe on trademarks or copyrights.  If you don't have permission to use a trademarked name or image, please do not submit your add-on to <?=SITE_NAME?>.  If your add-on includes code that is copyrighted by someone else, and is not licensed to you to use in your add-on, please do not submit your add-on to <?=SITE_NAME?>.  (If the holder of a trademark or copyright objects to the use of their trademark, we will very likely have to have the request for removal reviewed by counsel, and we will remove the add-on if it's deemed legally necessary.  This is an expensive process in terms of the project's resources, including time and money, so we ask you to be respectful and not cause us undue difficulty.)</p>
 
 <p>If you're not sure if the name of your add-on, or use of something within it, will prevent it from being listed on the site, you can ask amo-editors@mozilla.org for guidance.  IMPORTANT: Please note that this group is not able to provide legal advice, and that even if we feel that your usage is acceptable, we may revisit that decision in light of complaints from rights-holders and advice from legal counsel.</p>
 
-<p>In terms of reuse of source code from other add-ons, if the author has not clearly stated that you are permitted to use her code in your own work -- such as by placing it under an open source license -- then you should assume that you do not have the right to do so.  You can contact the author to seek such permission, but we can't provide you with any special rights to it just because it's been on AMO, or because the author isn't responding to your request.  (And, again, we can't provide legal advice, just advice about how your add-on is likely to interact with the policies of the site.)</p>
+<p>In terms of reuse of source code from other add-ons, if the author has not clearly stated that you are permitted to use her code in your own work -- such as by placing it under an open source license -- then you should assume that you do not have the right to do so.  You can contact the author to seek such permission, but we can't provide you with any special rights to it just because it's been on <?=SITE_NAME?>, or because the author isn't responding to your request.  (And, again, we can't provide legal advice, just advice about how your add-on is likely to interact with the policies of the site.)</p>
 
 <p>This applies to the Mozilla Foundation's trademarks as well, including "Mozilla", "Firefox", and "Thunderbird".  The Mozilla policy on trademark use is designed to protect against confusion, and prevent the trademarks from being overturned due to lack of protection; please respect the need for such protection, and help us preserve some of the most valuable assets of the Mozilla Foundation.</p>
 
 <h2>What happens after I nominate something?</h2>
 
-<p>Once your add-on has been nominated, it is evaluated by a team of AMO Editors according to the criteria described above.  If it is deemed ready for public display, it will be pushed to the public side once it has been evaluated, and you will receive an email notification.</p>
+<p>Once your add-on has been nominated, it is evaluated by a team of <?=SITE_NAME?> Editors according to the criteria described above.  If it is deemed ready for public display, it will be pushed to the public side once it has been evaluated, and you will receive an email notification.</p>
 
-<p>If we feel that the add-on isn't appropriate for the public side of AMO at this time, you'll receive an email notification indicating why, and your nomination will be removed from the queue.  If and when you feel that you've addressed the concerns expressed in that notification, and you want to be evaluated again, you can do so at your discretion.  Repeated nominations without meaningful improvements in the add-on are not looked upon with favour, so please do exercise discretion; you are more likely to anger us than to wear us down.</p>
+<p>If we feel that the add-on isn't appropriate for the public side of <?=SITE_NAME?> at this time, you'll receive an email notification indicating why, and your nomination will be removed from the queue.  If and when you feel that you've addressed the concerns expressed in that notification, and you want to be evaluated again, you can do so at your discretion.  Repeated nominations without meaningful improvements in the add-on are not looked upon with favour, so please do exercise discretion; you are more likely to anger us than to wear us down.</p>
 
 <h2>Can I nominate someone else's add-on?</h2>
 
-<p>Currently, we ask that an add-on's author nominate their own work for publication.  We want to make sure that the author is comfortable with the increased exposure and that feel the add-on in its current state appropriately reflects the quality of their work.  If you believe that an add-on is polished, that the author is abiding by the letter and spirit of the AMO policies, and that it would benefit Firefox, our users, and the web in general to have it made available to nearly a hundred million users around the world, you should feel free to encourage the author of the add-on to nominate their creation.</p>
+<p>Currently, we ask that an add-on's author nominate their own work for publication.  We want to make sure that the author is comfortable with the increased exposure and that feel the add-on in its current state appropriately reflects the quality of their work.  If you believe that an add-on is polished, that the author is abiding by the letter and spirit of the <?=SITE_NAME?> policies, and that it would benefit Firefox, our users, and the web in general to have it made available to nearly a hundred million users around the world, you should feel free to encourage the author of the add-on to nominate their creation.</p>
 
 <h2>My add-on has been in the nomination queue for a long time, do you hate me?</h2>
 
-<p>We don't hate you.  We love add-on developers, and we work hard to make them happy and productive, so that users all over the world can benefit from their work.  But being on the public side of AMO has value precisely because we take care in what ends up there, so we can't rush just to make it go faster.  We appreciate that it can be frustrating to wait for your add-on to be evaluated, and we want to keep the turnaround time as short as possible.  The more people provide careful and clear reviews of add-ons in the sandbox, the easier it is to perform these evaluations, so you might also consider helping out on that side if you're so inclined.</p>
+<p>We don't hate you.  We love add-on developers, and we work hard to make them happy and productive, so that users all over the world can benefit from their work.  But being on the public side of <?=SITE_NAME?> has value precisely because we take care in what ends up there, so we can't rush just to make it go faster.  We appreciate that it can be frustrating to wait for your add-on to be evaluated, and we want to keep the turnaround time as short as possible.  The more people provide careful and clear reviews of add-ons in the sandbox, the easier it is to perform these evaluations, so you might also consider helping out on that side if you're so inclined.</p>
 
 <h2>I found a serious bug in my add-on, and I really want to get the fix up there quickly.  What should I do?</h2>