Merge branch 'master' into patch-1

Author: koaning

.typo-ci.yml

@@ -0,0 +1,160 @@
+# This is a sample .typo-ci.yml file, it's used to configure how Typo CI will behave.
+# Add it to the root of your project and push it to github.
+---
+
+    # What language dictionaries should it use? Currently Typo CI supports:
+    # de
+    # en
+    # en_GB
+    # es
+    # fr
+    # it
+    # pt
+    # pt_BR
+    dictionaries:
+        - en
+    
+    # # Any files/folders we should ignore?
+    excluded_files:
+        - "*.py"
+        - "*.css"
+        - "*.yml"
+        - "*.html"
+        - "*.json"
+        - "*.md"
+        - "CHANGELOG.rst"
+        - "CODE_OF_CONDUCT.md"
+        - "CONTRIBUTING.md"
+        - "Dockerfile"
+        - "LICENSE.txt"
+        - "Makefile"
+        - "NOTICE"
+        - "README.md"
+        - "binder"
+        - "changelog"
+        - "cloudbuild.yaml"
+        - "data"
+        - "docker"
+        - "examples"
+        - "poetry.lock"
+        - "pyproject.toml"
+        - "rasa"
+        - "rasa_core"
+        - "rasa_nlu"
+        - "scripts"
+        - "secrets.tar.enc"
+        - "setup.cfg"
+        - "tests"
+        - ".codeclimate.yml"
+        - ".coveragerc"
+        - ".deepsource.toml"
+        - ".dockerignore"
+        - ".env"
+        - ".git"
+        - ".gitattributes"
+        - ".github"
+        - ".gitignore"
+        - ".pre-commit-config.yaml"
+        - ".typo-ci.yml"    
+    
+    # # Any typos we should ignore?
+    excluded_words:
+        - analytics
+        - asyncio
+        - bot
+        - bot's
+        - cmdline
+        - conveRT
+        - ConveRTFeaturizer
+        - ConveRTTokenizer
+        - crfsuite
+        - custom-nlg-service
+        - daksh
+        - db's
+        - deque
+        - non-latin
+        - deduplicate
+        - deduplication
+        - donath
+        - matplotlib
+        - extractor
+        - fbmessenger
+        - featurization
+        - featurized
+        - featurizer
+        - featurizers
+        - featurizes
+        - featurizing
+        - forni
+        - instaclient
+        - jwt
+        - jwt's
+        - jupyter
+        - jupyterhub
+        - karpathy
+        - keras
+        - knowledgebase
+        - knowledgebasebot
+        - linenos
+        - luis
+        - matmul
+        - mattermost
+        - memoization
+        - miniconda
+        - mitie
+        - mitie's
+        - dataset
+        - mongod
+        - mrkdown
+        - mrkdwn
+        - mymodelname
+        - myuser
+        - numpy
+        - networkx
+        - nlu
+        - nlu's
+        - perceptron
+        - pika
+        - pika's
+        - jieba
+        - pretrained
+        - pycodestyle
+        - pykwalify
+        - pymessenger
+        - pyobject
+        - python-engineio
+        - pre
+        - customizable
+        - quickstart
+        - rasa
+        - rasa's
+        - readthedocs
+        - repo
+        - rst
+        - sanic
+        - sanitization
+        - scipy
+        - sklearn
+        - spacy
+        - ish
+        - spaCy
+        - spaCy's
+        - README
+        - crf
+        - backends
+        - whitespaced
+        - ngram
+        - subsampled
+        - testagent
+        - tokenize
+        - tokenized
+        - tokenization
+        - tokenizer
+        - tokenizers
+        - typoci
+        - unfeaturized
+        - unschedule
+        - wsgi
+        - ruamel
+       ##
+    spellcheck_filenames: false

docs/api/event-brokers.rst

@@ -22,7 +22,7 @@ also known as a message broker, to forward Rasa :ref:`events` from the Rasa serv
 Format
 ------
 
-All events are streamed to the broker as serialised dictionaries every time
+All events are streamed to the broker as serialized dictionaries every time
 the tracker updates its state. An example event emitted from the ``default``
 tracker looks like this:
 
@@ -160,7 +160,7 @@ The code below shows an example on how to instantiate a Kafka producer in you sc
     tracker_store = InMemoryTrackerStore(domain=domain, event_broker=kafka_broker)
 
 
-The host variable can be either a list of brokers adresses or a single one.
+The host variable can be either a list of brokers addresses or a single one.
 If only one broker address is available, the client will connect to it and
 request the cluster Metadata.
 Therefore, the remain brokers in the cluster can be discovered
@@ -199,7 +199,7 @@ previously configured in the broker server.
 
 
 If the clients or the brokers in the kafka cluster are located in different
-machines, it's important to use ssl protocal to assure encryption of data and client
+machines, it's important to use ssl protocol to assure encryption of data and client
 authentication. After generating valid certificates for the brokers and the
 clients, the path to the certificate and key generated for the producer must
 be provided as arguments, as well as the CA's root certificate.

docs/api/rasa-sdk.rst

@@ -116,10 +116,10 @@ Details of the ``dispatcher.utter_message()`` method:
 
 .. _custom_session_start:
 
-Customising the session start action
+Customizing the session start action
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The default behaviour of the session start action is to take all existing slots and to
+The default behavior of the session start action is to take all existing slots and to
 carry them over into the next session. Let's say you do not want to carry over all
 slots, but only a user's name and their phone number. To do that, you'd override the
 ``action_session_start`` with a custom action that might look like this:

docs/api/tracker.rst

@@ -10,7 +10,7 @@ Tracker
 .. edit-link::
 
 Trackers maintain the state of a dialogue between the assistant and the user in the form
-of conversation sessions. To learn more about how to configure the session behaviour,
+of conversation sessions. To learn more about how to configure the session behavior,
 check out the docs on :ref:`session_config`.
 
 .. edit-link::

docs/core/domains.rst

@@ -370,6 +370,6 @@ be triggered at the very beginning of conversations).
   A session start triggers the default action ``action_session_start``. Its default
   implementation moves all existing slots into the new session. Note that all
   conversations begin with an ``action_session_start``. Overriding this action could
-  for instance be used to initialise the tracker with slots from an external API
+  for instance be used to initialize the tracker with slots from an external API
   call, or to start the conversation with a bot message. The docs on
   :ref:`custom_session_start` shows you how to do that.

docs/core/knowledge-bases.rst

@@ -401,7 +401,7 @@ The knowledge base action would detect that the user wants to obtain the value o
 If no mention or object was detected by the NER, the action assumes the user is referring to the most recently
 mentioned object, "PastaBar".
 
-You can disable this behaviour by setting ``use_last_object_mention`` to ``False`` when initializing the action.
+You can disable this behavior by setting ``use_last_object_mention`` to ``False`` when initializing the action.
 
 
 Customization

docs/core/old-core-change-log.rst

@@ -273,7 +273,7 @@ Fixed
 - fixed interactive learning to properly submit executed actions to the action
   server
 - allow the specification of the policy configuration while using the
-  visualisation script
+  visualization script
 - use default configuration if no policy configuration is passed
 - fixed html delivery from interactive server script (package compatible)
 - ``SlackBot`` when created in ``SlackInputChannel`` inherits the
@@ -440,7 +440,7 @@ Added
 Fixed
 -----
 - don't fail if rasa and rest input channels are used together
-- wrong paramter name in rocketchat channel methods
+- wrong parameter name in rocketchat channel methods
 - Software 2.0 link on interactive learning documentation page went to
   Tesla's homepage, now it links to Karpathy blogpost
 
@@ -514,7 +514,7 @@ Changed
 
 Changed
 -------
-- improved documentation for events (e.g. including json serialisation)
+- improved documentation for events (e.g. including json serialization)
 
 Removed
 -------
@@ -553,7 +553,7 @@ Added
   model metadata
 - more emoji support for PY2
 - intent confidence support in RegexInterpreter
-- added paramter to train script to pull training data from an url instead
+- added parameter to train script to pull training data from an url instead
   of a stories file
 - added new policy: :ref:`embedding_policy` implemented in tensorflow
 
@@ -797,7 +797,7 @@ Changed
 
 Fixed
 -----
-- fixed datetime serialisation of reminder event
+- fixed datetime serialization of reminder event
 
 [0.8.1] - 2018-02-01
 ^^^^^^^^^^^^^^^^^^^^
@@ -806,7 +806,7 @@ Fixed
 -----
 - removed deque to support python 3.5
 - Documentation improvements to tutorials
-- serialisation of date time value for ``ReminderScheduled`` event
+- serialization of date time value for ``ReminderScheduled`` event
 
 .. _corev0-8-0:
 
@@ -847,7 +847,7 @@ Changed
 Fixed
 -----
 - proper evaluation of stories with checkpoints
-- proper visualisation of stories with checkpoints
+- proper visualization of stories with checkpoints
 - fixed float slot min max value handling
 - fixed non integer feature decoding, e.g. used for memoization policy
 - properly log to specified file when starting Rasa Core server
@@ -861,7 +861,7 @@ Fixed
 
 Fixed
 -----
-- visualisation using Networkx version 2.x
+- visualization using Networkx version 2.x
 - add output about line of failing intent when parsing story files
 
 [0.7.8] - 2017-11-27

docs/core/old-core-migration-guide.rst

@@ -35,7 +35,7 @@ General
 
 Asynchronous First
 ~~~~~~~~~~~~~~~~~~
-- **No more flask.** The flask webserver has been replaced with an asyncronous
+- **No more flask.** The flask webserver has been replaced with an asynchronous
   webserver called Sanic. If you run the server in production using a wsgi
   runner, there are instructions here on how to recreate that with the
   sanic webserver:
@@ -126,7 +126,7 @@ Train script
   ``--fallback_action_name``), specify these in the policy config file instead,
   see :ref:`policy_file`
 
-Visualisation script
+visualization script
 ~~~~~~~~~~~~~~~~~~~~
 
 - You **must** pass a policy config flag with ``-c/--config`` now,

docs/core/policies.rst

@@ -118,7 +118,7 @@ You actually want to teach your policy to **ignore** the dialogue history
 when it isn't relevant and just respond with the same action no matter
 what happened before.
 
-You can alter this behaviour with the ``--augmentation`` flag.
+You can alter this behavior with the ``--augmentation`` flag.
 Which allows you to set the ``augmentation_factor``.
 The ``augmentation_factor`` determines how many augmented stories are
 subsampled during training. The augmented stories are subsampled before training
@@ -214,7 +214,7 @@ It is recommended to use ``state_featurizer=LabelTokenizerSingleStateFeaturizer(
           For example, if you set ``dialogue: [256, 128]``, we will add two feed forward layers in front of
           the transformer. The vectors of the input tokens (coming from the dialogue) will be passed on to those
           layers. The first layer will have an output dimension of 256 and the second layer will have an output
-          dimension of 128. If an empty list is used (default behaviour), no feed forward layer will be
+          dimension of 128. If an empty list is used (default behavior), no feed forward layer will be
           added.
           Make sure to use only positive integer values. Usually, numbers of power of two are used.
           Also, it is usual practice to have decreasing values in the list: next value is smaller or equal to the
@@ -362,7 +362,7 @@ It is recommended to use ``state_featurizer=LabelTokenizerSingleStateFeaturizer(
 
             There is an option to use linearly increasing batch size. The idea comes from
             `<https://arxiv.org/abs/1711.00489>`_. In order to do it pass a list to ``batch_size``, e.g.
-            ``"batch_size": [8, 32]`` (default behaviour). If constant ``batch_size`` is required, pass an ``int``,
+            ``"batch_size": [8, 32]`` (default behavior). If constant ``batch_size`` is required, pass an ``int``,
             e.g. ``"batch_size": 8``.
 
         .. note::

docs/core/reminders-and-external-events.rst

@@ -109,7 +109,7 @@ External Events
 ---------------
 
 Let's say you want to send a message from some other device to change the course of an ongoing conversation.
-For example, some moisture-sensor attached to a Raspberry Pi should inform your personal assistant that your favourite
+For example, some moisture-sensor attached to a Raspberry Pi should inform your personal assistant that your favorite
 plant needs watering, and your assistant should then relay this message to you.
 
 To do this, your Raspberry Pi needs to send a message to the `trigger_intent endpoint <../../api/http-api/#operation/triggerConversationIntent>`_ of your conversation.