Fix typos

This commit is contained in:
Andrea Gelmini 2021-04-28 20:29:44 +02:00 committed by Wim Taymans
parent 379068c31d
commit 47ef2b6b09
35 changed files with 53 additions and 53 deletions

View file

@ -417,7 +417,7 @@ int jack_set_freewheel_callback (jack_client_t *client,
void *arg) JACK_OPTIONAL_WEAK_EXPORT;
/**
* Tell JACK to call @a bufsize_callback whenever the size of the the
* Tell JACK to call @a bufsize_callback whenever the size of the
* buffer that will be passed to the @a process_callback is about to
* change. Clients that depend on knowing the buffer size must supply
* a @a bufsize_callback before activating themselves.
@ -606,7 +606,7 @@ int jack_set_xrun_callback (jack_client_t *client,
* register a latency callback.
*
* Another case is when a client wants to use
* @ref jack_port_get_latency_range(), which only returns meaninful
* @ref jack_port_get_latency_range(), which only returns meaningful
* values when ports get connected and latency values change.
*
* See the documentation for @ref jack_port_set_latency_range()

View file

@ -305,7 +305,7 @@ extern const char* JACK_METADATA_PORT_GROUP;
*
* This property allows audio ports to be tagged with a "meaning". The value
* is a simple string. Currently, the only type is "CV", for "control voltage"
* ports. Hosts SHOULD be take care to not treat CV ports as audibile and send
* ports. Hosts SHOULD be take care to not treat CV ports as audible and send
* their output directly to speakers. In particular, CV ports are not
* necessarily periodic at all and may have very high DC.
*/

View file

@ -61,11 +61,11 @@ jack_midi_get_event_count(void* port_buffer) JACK_OPTIONAL_WEAK_EXPORT;
*
* Jack MIDI is normalised, the MIDI event returned by this function is
* guaranteed to be a complete MIDI event (the status byte will always be
* present, and no realtime events will interspered with the event).
* present, and no realtime events will interspersed with the event).
*
* This rule does not apply to System Exclusive MIDI messages
* since they can be of arbitrary length.
* To maintain smooth realtime operation such events CAN be deliverd
* To maintain smooth realtime operation such events CAN be delivered
* as multiple, non-normalised events.
* The maximum size of one event "chunk" depends on the MIDI backend in use.
* For example the midiseq driver will create chunks of 256 bytes.

View file

@ -235,7 +235,7 @@ int jack_set_net_slave_shutdown_callback(jack_net_slave_t *net, JackNetSlaveShut
/**
* Prototype for server Restart callback : this is the new preferable way to be notified when the master has disappeared.
* The client may want to retry connecting a certain number of time (which will be done using the time_out value given in jack_net_slave_open)
* by returning 0. Otherwise returning a non-zero error code will definively close the connection
* by returning 0. Otherwise returning a non-zero error code will definitively close the connection
* (and jack_net_slave_is_active will later on return false).
* If both Shutdown and Restart are supplied, Restart callback will be used.
*

View file

@ -156,7 +156,7 @@ typedef struct _jack_session_event jack_session_event_t;
* whenever a session notification is sent via jack_session_notify().
*
* Ownership of the memory of @a event is passed to the application.
* It must be freed using jack_session_event_free when its not used anymore.
* It must be freed using jack_session_event_free when it's not used anymore.
*
* The client must promptly call jack_session_reply for this event.
*

View file

@ -63,7 +63,7 @@
* which means that their absence doesn't cause an error during program
* startup. Instead, Jill can test whether or not the symbol jack_set_latency_callback
* is null or not. If its null, it means that the JACK installed on this machine
* is too old to support this function. If its not null, then Jill can use it
* is too old to support this function. If it's not null, then Jill can use it
* just like any other function in the API. For example:
*
* \code