mirror of
https://github.com/zeek/zeek.git
synced 2025-10-06 00:28:21 +00:00
Spelling src
These are non-functional changes. * accounting * activation * actual * added * addresult * aggregable * aligned * alternatively * ambiguous * analysis * analyzer * anticlimactic * apparently * application * appropriate * arithmetic * assignment * assigns * associated * authentication * authoritative * barrier * boundary * broccoli * buffering * caching * called * canonicalized * capturing * certificates * ciphersuite * columns * communication * comparison * comparisons * compilation * component * concatenating * concatenation * connection * convenience * correctly * corresponding * could * counting * data * declared * decryption * defining * dependent * deprecated * detached * dictionary * directional * directly * directory * discarding * disconnecting * distinguishes * documentation * elsewhere * emitted * empty * endianness * endpoint * enumerator * essentially * evaluated * everything * exactly * execute * explicit * expressions * facilitates * fiddling * filesystem * flag * flagged * for * fragments * guarantee * guaranteed * happen * happening * hemisphere * identifier * identifies * identify * implementation * implemented * implementing * including * inconsistency * indeterminate * indices * individual * information * initial * initialization * initialize * initialized * initializes * instantiate * instantiated * instantiates * interface * internal * interpreted * interpreter * into * it * iterators * length * likely * log * longer * mainly * mark * maximum * message * minimum * module * must * name * namespace * necessary * nonexistent * not * notifications * notifier * number * objects * occurred * operations * original * otherwise * output * overridden * override * overriding * overwriting * ownership * parameters * particular * payload * persistent * potential * precision * preexisting * preservation * preserved * primarily * probably * procedure * proceed * process * processed * processes * processing * propagate * propagated * prototype * provides * publishing * purposes * queue * reached * reason * reassem * reassemble * reassembler * recommend * record * reduction * reference * regularly * representation * request * reserved * retrieve * returning * separate * should * shouldn't * significant * signing * simplified * simultaneously * single * somebody * sources * specific * specification * specified * specifies * specify * statement * subdirectories * succeeded * successful * successfully * supplied * synchronization * tag * temporarily * terminating * that * the * transmitted * true * truncated * try * understand * unescaped * unforwarding * unknown * unknowndata * unspecified * update * usually * which * wildcard Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
parent
d65c75e2ad
commit
cd201aa24e
188 changed files with 432 additions and 432 deletions
|
@ -155,7 +155,7 @@ public:
|
|||
template <class T> std::list<T*> Components() const;
|
||||
|
||||
/**
|
||||
* Returns the (dynamic) plugin associated with a given filesytem
|
||||
* Returns the (dynamic) plugin associated with a given filesystem
|
||||
* path. The path can be the plugin directory itself, or any path
|
||||
* inside it.
|
||||
*/
|
||||
|
@ -208,7 +208,7 @@ public:
|
|||
* for it. Normally a plugin receives events through HookQueueEvent()
|
||||
* only if Zeek actually has code to execute for it. By calling this
|
||||
* method, the plugin tells Zeek to raise the event even if there's no
|
||||
* correspondong handler; it will then go into HookQueueEvent() just as
|
||||
* corresponding handler; it will then go into HookQueueEvent() just as
|
||||
* any other.
|
||||
*
|
||||
* @param handler The event being interested in.
|
||||
|
@ -273,7 +273,7 @@ public:
|
|||
* If the plugins takes over by returning 1, there are two cases: if the
|
||||
* second tuple element remains unset, the plugin handled the loading
|
||||
* completely internally; the caller must not process it any further.
|
||||
* Alternatively, the plugin may optionally return the acutal content to
|
||||
* Alternatively, the plugin may optionally return the actual content to
|
||||
* use for the file as a string through the tuple's second element. If so,
|
||||
* the caller must ignore the file on disk and use that provided content
|
||||
* instead (including when there's actually no physical file in place on
|
||||
|
@ -493,7 +493,7 @@ private:
|
|||
using dynamic_plugin_map = std::map<std::string, std::string>;
|
||||
dynamic_plugin_map dynamic_plugins;
|
||||
|
||||
// We temporarliy buffer scripts to load to get them to load in the
|
||||
// We temporarily buffer scripts to load to get them to load in the
|
||||
// right order.
|
||||
using file_list = std::list<std::string>;
|
||||
file_list scripts_to_load;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue