Remove DEAFULT_LOCAL_SIZE from docs

Author: chudur-budur

docs/source/user_guide/kernel_programming/writing_kernels.rst

@@ -30,33 +30,6 @@ storing the result of vector summation:
    :name: ex_kernel_declaration_vector_sum
 
 
-.. Kernel Invocation
-.. ------------------
-
-.. When a kernel is launched you must specify the *global size* and the *local size*,
-.. which determine the hierarchy of threads, that is the order in which kernels
-.. will be invoked.
-
-.. The following syntax is used in ``numba-dpex`` for kernel invocation with
-.. specified global and local sizes:
-
-.. ``kernel_function_name[global_size, local_size](kernel arguments)``
-
-.. In the following example we invoke kernel ``kernel_vector_sum`` with global size
-.. specified via variable ``global_size``, and use ``numba_dpex.DEFAULT_LOCAL_SIZE``
-.. constant for setting local size to some default value:
-
-.. .. code-block:: python
-
-..    import numba_dpex as ndpx
-
-..    global_size = 10
-..    kernel_vector_sum[global_size, ndpx.DEFAULT_LOCAL_SIZE](a, b, c)
-
-.. .. note::
-..   Each kernel is compiled once, but it can be called multiple times with different global and local sizes settings.
-
-
 Kernel Invocation
 ------------------
 

docs/source/user_guide/programming_model.rst

@@ -161,7 +161,7 @@ Specifying the execution queue is done using Python context manager:
    with dpctl.device_context(q):
        # apply the kernel to elements of X, writing value into Y,
        # while executing using given queue
-       numba_dpex_poly[X.size, numba_dpex.DEFAULT_LOCAL_SIZE](X, Y)
+       numba_dpex_poly[numba_dpex.Range(X.size)](X, Y)
 
 The argument to ``device_context`` can be a queue object, a device object for
 which a temporary queue will be created, or a filter selector string. Thus we