Commit a82b365b authored by Josh Soref's avatar Josh Soref Committed by Tomasz Zawadzki
Browse files

spelling: doc 



Part of #2256

* accessible
* bstatic
* example
* initiator
* obvious
* privileged
* scenario
* transparent

Change-Id: I15f30f56e3bb18443c829830454360945878012a
Signed-off-by: default avatarJosh Soref <jsoref@gmail.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10401


Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
parent 70b16d44

doc/Doxyfile

+1 −1
Original line number Diff line number Diff line
@@ -1515,7 +1515,7 @@ EXT_LINKS_IN_WINDOW = NO 


FORMULA_FONTSIZE       = 10



# Use the FORMULA_TRANPARENT tag to determine whether or not the images

# Use the FORMULA_TRANSPARENT tag to determine whether or not the images

# generated for formulas are transparent PNGs. Transparent PNGs are not

# supported properly for IE 6.0, but are supported on all modern browsers.

#

doc/accel_fw.md

+2 −2
Original line number Diff line number Diff line
@@ -51,7 +51,7 @@ way needs to be certain that the underlying hardware exists everywhere that it r 
The low level library for IOAT is located in `/lib/ioat`.  The low level library

for DSA is in `/lib/idxd` (IDXD stands for Intel(R) Data Acceleration Driver).

In `/lib/idxd` folder, SPDK supports to leverage both user space and kernel space driver

to drive DSA devices. And the following describes each usage scenerio:

to drive DSA devices. And the following describes each usage scenario:



Leveraging user space idxd driver: The DSA devices are managed by the user space

driver in a dedicated SPDK process, then the device cannot be shared by another
@@ -59,7 +59,7 @@ process. The benefit of this usage is no kernel dependency. 


Leveraging kernel space driver: The DSA devices are managed by kernel

space drivers. And the Work queues inside the DSA device can be shared among

different processes. Naturally, it can be used in cloud native scenerio. The drawback of

different processes. Naturally, it can be used in cloud native scenario. The drawback of

this usage is the kernel dependency, i.e., idxd driver must be supported and loaded

in the kernel.

doc/gdb_macros.md

+1 −1
Original line number Diff line number Diff line
@@ -160,7 +160,7 @@ starting gdb is type "spdk_load_macros". 
.gdbinit can also be used in order to run automatically run the manual steps

above prior to starting gdb.



Exmaple .gdbinit:

Example .gdbinit:



~~~{.sh}

source /opt/km/install/tools/gdb_macros/gdb_macros.py

doc/iscsi.md

+1 −1
Original line number Diff line number Diff line
@@ -316,7 +316,7 @@ portal group may optionally have a redirect portal for non-discovery logins for 
each associated target. This redirect portal must be from a private portal group.



Initiators configure portals in public portal groups as target portals. When an

initator logs in to a target through a portal in an associated public portal group,

initiator logs in to a target through a portal in an associated public portal group,

the target sends a temporary redirection response with a redirect portal. Then the

initiator logs in to the target again through the redirect portal.

doc/jsonrpc.md

+1 −1
Original line number Diff line number Diff line
@@ -8473,7 +8473,7 @@ Example response: 


Request notifications. Returns array of notifications that happend since the specified id (or first that is available).



Notice: Notifications are kept in circular buffer with limited size. Older notifications might be inaccesible

Notice: Notifications are kept in circular buffer with limited size. Older notifications might be inaccessible

due to being overwritten by new ones.



#### Parameters