mirror of
				https://github.com/zulip/zulip.git
				synced 2025-11-04 05:53:43 +00:00 
			
		
		
		
	Remove some some duplicate words in copy.
This commit is contained in:
		@@ -28,7 +28,7 @@ changes take effect.  The Handlebars frontend HTML templates
 | 
			
		||||
`tools/compile-handlebars-templates` job, which runs as part of
 | 
			
		||||
`tools/run-dev.py`.
 | 
			
		||||
 | 
			
		||||
* If you change Python code used by the the main Django/Tornado server
 | 
			
		||||
* If you change Python code used by the main Django/Tornado server
 | 
			
		||||
processes, these services are run on top of Django's [manage.py
 | 
			
		||||
runserver][django-runserver] which will automatically restart the
 | 
			
		||||
Zulip Django and Tornado servers whenever you save changes to Python
 | 
			
		||||
 
 | 
			
		||||
@@ -12,7 +12,7 @@ describe 'ensure_resource' do
 | 
			
		||||
    let :pre_condition do
 | 
			
		||||
      'user { "dan": }'
 | 
			
		||||
    end
 | 
			
		||||
    it "should contain the the ensured resources" do
 | 
			
		||||
    it "should contain the ensured resources" do
 | 
			
		||||
      subject.should run.with_params('user', 'dan', {})
 | 
			
		||||
      compiler.catalog.resource('User[dan]').to_s.should == 'User[dan]'
 | 
			
		||||
    end
 | 
			
		||||
 
 | 
			
		||||
@@ -634,7 +634,7 @@ exports.respond_to_message = function (opts) {
 | 
			
		||||
    var pm_recipient = message.reply_to;
 | 
			
		||||
    if (opts.reply_type === "personal" && message.type === "private") {
 | 
			
		||||
        // reply_to for private messages is everyone involved, so for
 | 
			
		||||
        // personals replies we need to set the the private message
 | 
			
		||||
        // personals replies we need to set the private message
 | 
			
		||||
        // recipient to just the sender
 | 
			
		||||
        pm_recipient = message.sender_email;
 | 
			
		||||
    }
 | 
			
		||||
 
 | 
			
		||||
@@ -617,7 +617,7 @@
 | 
			
		||||
 | 
			
		||||
      <p>In the next screen, provide the details. First, click Add Actions to
 | 
			
		||||
      display the rule actions. Select "Trigger an App Action" in the dropdown, and
 | 
			
		||||
      then the name of the custom action you created earlier when the the second
 | 
			
		||||
      then the name of the custom action you created earlier when the second
 | 
			
		||||
      dropdown appears. You can add additional "All" or "Any" conditions if desired.
 | 
			
		||||
      Also select when the rule should run (if not "Anytime") and enable it.</p>
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user