summaryrefslogtreecommitdiff
path: root/svx/source/fmcomp
diff options
context:
space:
mode:
authorAndrea Gelmini <andrea.gelmini@gelma.net>2016-01-09 22:55:28 +0100
committerAshod Nakashian <ashnakash@gmail.com>2016-01-10 14:17:20 +0000
commit64d624b65124ac02d8ee59b135593fd9d8eb9067 (patch)
tree772fc0f308549b9416fbcb06bce2bf0e0f5809cc /svx/source/fmcomp
parentd61c16966b017abdbebf5ec0c2131de5a91c67f8 (diff)
Fix typos
Change-Id: I9a5940027423ff0791fa7da0b79b617412ce6b86 Reviewed-on: https://gerrit.libreoffice.org/21209 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Ashod Nakashian <ashnakash@gmail.com>
Diffstat (limited to 'svx/source/fmcomp')
-rw-r--r--svx/source/fmcomp/fmgridcl.cxx2
-rw-r--r--svx/source/fmcomp/fmgridif.cxx6
2 files changed, 4 insertions, 4 deletions
diff --git a/svx/source/fmcomp/fmgridcl.cxx b/svx/source/fmcomp/fmgridcl.cxx
index 2e5c50ce9006..ddd6a7046b62 100644
--- a/svx/source/fmcomp/fmgridcl.cxx
+++ b/svx/source/fmcomp/fmgridcl.cxx
@@ -1802,7 +1802,7 @@ Sequence< Any> FmGridControl::getSelectionBookmarks()
// navigation bar and the grid. The latter itself will result in SeekRow calls. So after (successfully) returning
// from the moveRelative the getPosition returns an invalid value. And so the SeekCursor fails.
// In the consequence ALL parts of code where two calls to the seek cursor are done, while the second call _relys_ on
- // the first one, should be secured against recursion, with a broad-minded interpretion of "recursion": if any of these
+ // the first one, should be secured against recursion, with a broad-minded interpretation of "recursion": if any of these
// code parts is executed, no other should be accessible. But this sounds very difficult to achieve...
// )
diff --git a/svx/source/fmcomp/fmgridif.cxx b/svx/source/fmcomp/fmgridif.cxx
index 041825e5a55f..3cef94fd240c 100644
--- a/svx/source/fmcomp/fmgridif.cxx
+++ b/svx/source/fmcomp/fmgridif.cxx
@@ -495,7 +495,7 @@ void SAL_CALL FmXGridControl::createPeer(const Reference< css::awt::XToolkit >&
// consider the following ugly scenario: updateFromModel leads to a propertiesChanges on the Control,
// which determines, dat a "critical" property has changed (e.g. "Border") and therefore starts a new
- // Peer, which lands again here in createPeerm we also start a second FmXGridPeer and initialise it.
+ // Peer, which lands again here in createPeer we also start a second FmXGridPeer and initialise it.
// Then we exit from the first incarnation's updateFromModel and continue working with the pPeer,
// that is in fact now already obsolete (as another peer is being started in the second incarnation).
// Therefore the effort with the PeerCreationLevel, which ensures that we really use the Peer
@@ -1776,7 +1776,7 @@ void FmXGridPeer::elementReplaced(const ContainerEvent& evt) throw( RuntimeExcep
// set the model of the new column
DbGridColumn* pCol = pGrid->GetColumns().at( nNewPos );
- // for initializong this grid column, we need the fields of the grid's data source
+ // for initializing this grid column, we need the fields of the grid's data source
Reference< XColumnsSupplier > xSuppColumns;
CursorWrapper* pGridDataSource = pGrid->getDataSource();
if ( pGridDataSource )
@@ -2093,7 +2093,7 @@ void FmXGridPeer::dispose() throw( RuntimeException, std::exception )
// tell the interceptor it has a new (means no) predecessor
xInterceptor->setMasterDispatchProvider( nullptr );
- // ask for it's successor
+ // ask for its successor
Reference< XDispatchProvider > xSlave = xInterceptor->getSlaveDispatchProvider();
// and give it the new (means no) successoert
xInterceptor->setSlaveDispatchProvider( nullptr );